We have a customer that refuses to accept the idea of multiple instances. I'
ve told them that there are no hidden problems with this. On the contrary th
ere are a number of advantages if you're going to consolidate a huge number
of servers with databases t
hat have different requirements. Interesting to hear some comments about the
subject!?Hi Folke,
apart from a bit of wasted space caused throug multiple server-engines i
dont see any problems doing so.
Micha
"Folke" <anonymous@.discussions.microsoft.com> schrieb im Newsbeitrag
news:8B57E51F-1A7F-4D2C-83F2-2B01F915DADC@.microsoft.com...
> We have a customer that refuses to accept the idea of multiple instances.
I've told them that there are no hidden problems with this. On the contrary
there are a number of advantages if you're going to consolidate a huge
number of servers with databases that have different requirements.
Interesting to hear some comments about the subject!?|||It's best to run a single instance on a server unless you have a specific
reason to do otherwise. This will make the best use of available hardware
resources. Consolidating many databases onto a single instance is possible
as long as you don't have conflicting application requirements like
different default instance collations.
See the Books Online <architec.chm::/8_ar_cs_5upf.htm> for some guidelines.
Hope this helps.
Dan Guzman
SQL Server MVP
"Folke" <anonymous@.discussions.microsoft.com> wrote in message
news:8B57E51F-1A7F-4D2C-83F2-2B01F915DADC@.microsoft.com...
> We have a customer that refuses to accept the idea of multiple instances.
I've told them that there are no hidden problems with this. On the contrary
there are a number of advantages if you're going to consolidate a huge
number of servers with databases that have different requirements.
Interesting to hear some comments about the subject!?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment