Issue happened with MOSS 2007

Problem
We have SharePoint server 2007 connected to the production environment with the SQL Data base name WSS_Content_P. Due to some technical changes we by mistake triggered the Production Front end to the Test environment Database that is WSS_Content_T . Here the Test database was just the replica of the production database with difference of 2 days. Now after some days we got to know that such a problem has been created. We found that business data of 2 days was missing from the database.
Solution : In the End we came to solution to any how sync the two databases. Now we needed the best database comparison tool to check the data from the two database server.
Tool Used:  VISUAL STUDIO
Internal Tool : SQL > DATA COMPARE
·         Click the Data compare option in visual studio.
·         Provide the connection to both the databases, one will be source and other will be the destination.
·         Now we have four different option
o   Different Records: Scans all the records in the database on the basics of primary keys to find the updates and changes.
o   Only in Source: Compares both the databases for the different rows in the source database.
o   Only in Destination: Compare both the databases for the different rows in the destination, after this we can create a script which deletes the extra file from the destination.
o   Identical records: Compare and provides the list of identical fields in the database.
·         After this it shows a comparison summary.
·         This click script button in the tool bar. This will create a query for required data change.
·         Run this query script on the production database. And reconnected the databases. 
In our case we require the data from the source to the destination, where source is the test environment and destination is the production environment.
NOTE: KINDLY TAKE THE BACKUP OF BOTH THE DATABASES TO HAVE DATA SECURITY
What we did to resolve our Problem.
1.       Selecting the Test database as source and destination as production database.
2.       Then selecting the different records and only insource option we move forwarded.
3.       A comparison summary was created which we analyzed before going further to know that we are having the correct data changes. We checked for update queries.
4.       Then we executed the queries on the production environment.

5.       Then we connected the databases back to the frontend and check to get the desired output.

Comments

Popular posts from this blog

How to use lamda expression for updating using LINQ

using session for login and logout in asp.net

How to post data in MVC using form collection for Beginners.