Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Scott
Posting Yak Master
145 Posts |
 Posted - 2007-05-17 : 13:31:19
|
| I work for a mid size company with the usual collection of enterprise applications. We are trying to consolidate our SQL environment consisting of around 100 databases none of which are over 100GB with the average database size around 5GB. Recently a large server was purchased as the "Big Daddy" SQL box. Obviously not all the databases will be moved to this one box but within reason a number can.My question: What is the best way to configure the box?1 OS & 1 Default Instance - How do we isolate loops memory leaks etc...1 OS & Multiple instances, ie:Dedicated instance for each application. - How do you allocate CPU & memory, allow for optimum performance without putting others at risk from a rouge process?Virtualized OS for each application with a default instance - Too much overhead impacts performance?Future plans include offsite replication, perhaps mirroring with failover.I'd appreciate anyone else's thoughts ideas? How have you tackled this problem in your environment?ThanksScott |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-05-17 : 16:18:53
|
| I'll not create multiple instances on 32 bit server, can't allocate memory effectively. |
 |
|
|
|
|
|
Single Instance/Multiple Instance/Virtualization Q