Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Performance of 64 bit SQL Server 2008 with multiple applications


Performance of 64 bit SQL Server 2008 with multiple applications

Author
Message
ITDevelopment 87561
ITDevelopment 87561
Forum Newbie
Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: General Forum Members
Points: 1 Visits: 5
We are purchasing a new 64 bit Intel Xeon 4 core sql server box 2008 with 256 GB RAM connected to high speed 15 K drives with fibre disc.

We are planning to consolidate our 3 sql server instances onto this one instance. Currently, the combined number of connections are roughly 400 and using around 50 GB RAM.

The new instance would therefore run around 15 applications that was previously divided into 3 instances. Are there any areas for concern regarding the performance of the new box. Is there anything else for me to consider/monitor/measure before we commit to doing this?

Do you think that having multiple instances on the same box would increase performance or would it be better to have instances on separate boxes.
Slawek Guzek
Slawek Guzek
SSC Journeyman
SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)SSC Journeyman (94 reputation)

Group: General Forum Members
Points: 94 Visits: 245
Multiple instances are used not for increase overall performance, but for increase manageability.

One instance or three all share the same physical resources.

In my opinion one instance is better from performance point of view because SQL can optimize resource usage across all databases, while in 3 instances servers does not communicate with each other but compete for memory, CPU and disks.

You can use separate instances if you want to increase performance of one or few specific databases.
You may want to guarantee some memory and performance advantage to some particular databases. Then run this specific databases in separate instance and use minimum server memory for that instance. You can also make some CPUs available to one instance while not available to the rest.

Regards,
Slawek
Nadrek
Nadrek
Ten Centuries
Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)Ten Centuries (1.2K reputation)

Group: General Forum Members
Points: 1216 Visits: 2698
+1 to the prior poster.

I use multiple instances to use one physical machine and OSE (Operating System Environment) to serve up multiple copies of "the same" application database for different uses; one instance per developer, and the developers can restore from backups or make backups within the disk quota limits as they see fit (create a known starting point with whatever test data they need, and run tests from a well known starting point over and over).

For real production when you can combine databases properly (i.e. they all have different names), I'd use a single instance, and allow whichever needs it to use the resources required. All the usual caveats on virtualization apply; don't put two apps that need the full physical power during overlapping time periods on the same hardware, or they'll slow each other down. If one needs it Monday mornings, and another needs it every afternoon, you're fine. If they both need to meet SLA's at the same time... don't combine them casually.
SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)SSC-Insane (23K reputation)

Group: General Forum Members
Points: 23012 Visits: 18262
I agree with the others on this.

One thing to note is that 15 applications / or 15 databases is not a burden for SQL server in many cases. There are other factors such as usage and how well the code is written and maintenance of the server that will affect overall performance for your apps.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search