Target Content Database using TA_SiteCollections.aspx
-
Friday, September 23, 2011 8:26 PM
Using Tenant Administation page, Manage Site Collection; is it possible for new site collection to be created into a specific content database?
Would like each tenants' Site Collections to reside within same content DB, and not commingle them.
All Replies
-
Tuesday, September 27, 2011 8:19 AMModerator
Hi,
You can use powershell cmdlet move-spsite to realize it.
Note:
The Move-SPSite cmdlet moves the data in the specified site collection from its current content database to the content database specified by the DestinationDatabase parameter. A no-access lock is applied to the site collection to prevent users from altering data within the site collection while the move is taking place. Once the move is complete, the site collection is returned to its original lock state. The destination content database specified must already exist, must be attached to the same SQL Server as the site collection's current content database, and must be attached to the site collection's current Web application.
http://technet.microsoft.com/en-us/library/ff607915.aspx
Regards,
Seven
-
Wednesday, September 28, 2011 1:52 PM
This requires a reactive, not proactive administration step, so it is just better to not allow Self-Service Site Creation; and have administrator provision new site using PowerShell New-SPSite command /w these settings: -HostHeaderWebApplication $webApp -ContentDatabase $contentDB –SiteSubscription $subscription
So I guess the Tenant Administration page should disable the 'New' button when "Use Self-Service Site Creation" permission is denied. It is not, so attempting to add a new site collection results in an error.
Maybe both of these issues can be fixed in the future.

