g3
Noobie
Posts: 4 
|
Post by g3 on Feb 19, 2009 18:23:51 GMT -6
Currently we have 7 content database hosted in one SQL server instance. We would like to scale out our sharepoint content database to multiple sql server instances so that the current SQL server is not overloaded.
[/li][li]Is this a supported option?
[/li][li]Are there any best practices/reference architecture to support this scenario?
|
|
|
|
Post by Jay Mueller on Feb 23, 2009 10:50:42 GMT -6
Your best bet is to setup a SQL Cluster and point your SharePoint farm at the cluster. SQL Clustering services will help mitigate load. Hope this helps!
|
|
g3
Noobie
Posts: 4
|
Post by g3 on Feb 25, 2009 14:34:09 GMT -6
Thanks for the response Jay.
Sorry, I forgot to mention in my earlier post that our current SQL server is already clustered using MSCS.
We see SQL server CPU spikes when Users perform certain SharePoint operations. We are now looking into the option of scaling out SQL server and put the databases which cause the spikes into them as against scaling up the current instance with more CPU's.
|
|
