Comments on: Single Instance vs Multiple Instances http://itknowledgeexchange.techtarget.com/sql-server/single-instance-vs-multiple-instances/ Wed, 25 Nov 2009 16:53:56 +0000 http://wordpress.org/?v=2.6.2 By: Mldba http://itknowledgeexchange.techtarget.com/sql-server/single-instance-vs-multiple-instances/#comment-251 Mldba Fri, 21 Aug 2009 12:45:25 +0000 http://itknowledgeexchange.techtarget.com/sql-server/single-instance-vs-multiple-instances/#comment-251 One other reason that may drives the decision to take more than one instance is SLA. We can have one instance where databases are available during business hours and one instance where databases are available 24/7. One other reason that may drives the decision to take more than one instance is SLA. We can have one instance where databases are available during business hours and one instance where databases are available 24/7.

]]> By: Crunchie http://itknowledgeexchange.techtarget.com/sql-server/single-instance-vs-multiple-instances/#comment-245 Crunchie Thu, 06 Aug 2009 15:39:32 +0000 http://itknowledgeexchange.techtarget.com/sql-server/single-instance-vs-multiple-instances/#comment-245 [I]Another place where you may see some pain is your tempdb performance (assuming that both instances use the same tempdb). [/I] Different instances cannot share tempdb. Databases in the same instance do. Sharing physical disks is a whole different issue and affects not just tempdb but all databases. RAM is probably one of the easiest issues to address when running multi-instance. It becomes a nightmare to manage in a single instance unless you are running SQL Server 2008 Enterprise Edition with Resource Governor. Even then, it's better, not truly easy. Availability, collation (as per Robboek's comment) and jobs are also tough issues to address in a single instance with multiple DBs. Another place where you may see some pain is your tempdb performance (assuming that both instances use the same tempdb).

Different instances cannot share tempdb. Databases in the same instance do. Sharing physical disks is a whole different issue and affects not just tempdb but all databases.

RAM is probably one of the easiest issues to address when running multi-instance. It becomes a nightmare to manage in a single instance unless you are running SQL Server 2008 Enterprise Edition with Resource Governor. Even then, it’s better, not truly easy.

Availability, collation (as per Robboek’s comment) and jobs are also tough issues to address in a single instance with multiple DBs.

]]> By: Robboek http://itknowledgeexchange.techtarget.com/sql-server/single-instance-vs-multiple-instances/#comment-243 Robboek Mon, 03 Aug 2009 17:54:17 +0000 http://itknowledgeexchange.techtarget.com/sql-server/single-instance-vs-multiple-instances/#comment-243 One reason you might need to run multiple instances is the collation of system databases, especially tempdb. One reason you might need to run multiple instances is the collation of system databases, especially tempdb.

]]>