You certainly could, although it would be a choice of something like a master job server. When you say that the instances are virtual, you have to keep in mind that a virtual instance is licensed the same as a physical one.
Buck Woody
SQL Server Technical Specialist - Microsoft
(425) 707-4863
http://blogs.msdn.com/buckwoody
https://academymobile.microsoft.com/pages/podcasterdetail.aspx?aid=739
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced.
From: kghammond
[mailto:notifications@codeplex.com]
Sent: Monday, August 31, 2009 12:55 PM
To: woodyb@hotmail.com
Subject: Maintenance and Backups [SQLCMS:67512]
From: kghammond
Is this infrastructure feasible to create centralized mainteinance and backup scripts and to monitor them centrally?
One of the challenges we are observing are many 3rd party applications that need a SQL server for configuration and managment data. These applications fail without a SQL server but many times they only store a few hundred MB or a handful of GB of data. These are not data warehouses. So you really have two options. Locate all of these in one cluster so if you have issues with this cluster, all these 3rd party apps begin to fail, or locate these SQL server instances alongside the applications. In our enviornment, almost 100% virtual, there is no licensing implication of sprawling SQL server instanaces. It really boils down to a management and administation issue.
Thoughts?
