STSADM restore errors with “No content databases are available for this operation”
By peter.stilgoe
The problem is probably that the GUID of the new site youre trying to restore is the same as an existing site in the content database. Either delete the existing site or I would imagine you could restore to a diffrent content database although I havnt verified this.
More From pstilgoe
Sharepoint – Creating Content Databases
By peter.stilgoe
When you create a content database in Sharepoint through the central admin it is created with the following characteristics:
Recovery Model: FULL
Auto growth: 1mb
Log file growth: 10%
The one we are concerned with here is the Auto growth being set to 1mb. This means is we upload a 50mb file, the Db has to grow 50 x 1mb which causes performance issues. Also if a database auto grow occurs whilst being used by end users all web sites inside that site collection will stop while the database allocates more space. Also you will be pretty much guaranteed to get database fragmentation.
Its better to create your content databases manually and set the size you expect it to grow to from the outset. Then set a quota in Sharepoint so that the DB cant grow any more once it hits the size limit.
Note: if you do create via SQL ensure the DB settings are Latin1_General_CI_AS_KS_WS



March 24th, 2010
