subject: SharePoint Recovery When STSADM MergeContentDB Cause Corruption [print this page] SharePoint Recovery When STSADM MergeContentDB Cause Corruption
Microsoft sharepoint allows you to move site collection one content database to another. You can use STSADM MergeContentDB command for the same. For this, you are required to define source and destination database correctly. However, in some cases, STSADM MergeContentDB may fail to work properly and cause database corruption. In such situations, you need to opt for SharePoint recovery solutions to get your valuable data back.
In order to successfully move the site collection, both the destination and source database must be attached. The failure of this process depends upon various factors, such as size of the site collection, load of Microsoft SQL Server database, and user traffic.
Cause of Database Corruption
The problem usually occurs if you try to merge a site collection whose size is 10 GB or larger. The corruption may affect both source and destination databases and you need to recover SharePoint database to extract your precious data.
How to Fix Corruption Caused by STSADM MergeContentDB?
To sort out the corruption issue, you need to take the below precautions while using STSADM MergeContentDB command-
Create a complete backup of both destination and source database before starting the migration process.
Avoid canceling the migration operation on SQL Server or front-end Web server.
Run the command during off-peak time as it places high load on SQL Server.
If you have a damaged database and want to recover SharePoint documents, then above steps can not help you. In such cases, you are required to opt for SharePoint database recovery tools to recover sharepoint site
SharePoint recovery tools are specifically designed to recover SharePoint 2007 and 2010 databases in all corruption scenarios. The applications help you perform easy and safe SharePoint repair with interactive user interface and read-only conduct.
