SharePoint 2013 - Split Site Collections between different SQL Servers - (not a single site collection)

I have a requirement to be able to create site collections (from the same Web App) between not only different content databases (which I know how to do), but to also be able to spread the web app as well as site collections over different SQL servers, (without using SQL alias or clustering or any type of name consolidation.) In other words, when a site collection is created be able to say this one goes to server1\sqlinstance and this one goes to server2\sqlinstance, all within the same web app.

I can imagine it being possible, but again I can also imagine it being not possible, and I am leaning that direction. If any one has any concrete information, a tech net article would be great, please let me know.

Thanks
LVL 22
Walter CurtisSharePoint AEDAsked:
Who is Participating?
 
Ted BouskillSenior Software DeveloperCommented:
I went through this article and it seems to have everything you need to move a site collection to another database server added to a farm.

http://technet.microsoft.com/en-us/library/cc262781(v=office.15).aspx

Note: You can't split the collection data between servers.  I doubt Microsoft would ever support that
0
 
Walter CurtisSharePoint AEDAuthor Commented:
Thanks very much for the information. That is what I was looking for.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.