New answers tagged content-database
As you are restoring a DB backup from a different farm (PROD to DEV), I believe you should dismount the DB (using Central Administration UI or PowerShell commandlet Dismount-SPContentDatabase) before restoring a content database, and then re-mount after restore. This takes care of the synchronization with the configuration database and also lets you specify ...
Their are many reasons for a object to become Orphan. if you delete a user from the AD but that user still present in SharePoint, now this user is called Orphan. You are trying to provision a Site collection and their is interruption during the provision process, now that site collection will become orphan. You deploy the a feature/solution then later ...
According to the information you provided, two things make sure. Farm Account and App Pool Account should Have the DBO rights on the restored DB. DB is not offline. Also if their is any error share with us.
After a day of pouring over different solutions, we found that the problem wasn't actually with SharePoint, but rather was a problem with our sql server cluster. After upgrading from SP1 to SP3 this error was resolved.
I wrote a blog series on bad access patterns to the SharePoint content database: http://apmblog.compuware.com/2010/03/18/how-to-avoid-the-top-5-sharepoint-performance-mistakes/ - we keep seeing the same mistakes from developers - assuming that SharePoint's List Model allows high transaction volume with high performance. Well - unfortunately thats not what ...
Top 50 recent answers are included