This post is about the relationship between an issue with the STSADM –o mergecontentdbs (also for splitting), a possible hot fix and issues with orphaned objects or corrupt database.
Remember the event log entries about:
failure trying to synch site <SITEGUID>for ContentDB <ContentDBGUID> WebApp <WebAppGUID>. Exception message was Cannot insert duplicate key row in object ‘dbo.UserMemberships’ with unique index ‘CX_UserMemberships_RecordId_MemberGroupId_SID’.
The statement has been terminated..
Well, possibly you have orphaned objects in your database. But how force that have happened. Various reasons but there is one that has been introduced reasonably recently: the STSADM –o mergecontentdbs command that was launched with SP1 I judge.
Anyhow, you can use it for splitting make pleased databases. You know, one of your make pleased databases becomes to huge. You start analyzing the site collections and choose to go a number of the huge ones to their own new make pleased db. First you’ll have to generate a xml file by Stsadm –o enumsites –url …. –filename … (or something like that). Edit the file, delete the collections that should wait and save the file.
Next you run the mergecontentdbs command with operation 3 and the file as input. That force go well or not, depends if you have installed a hot fix. 
The mergecontentdbs command may lead to information loss (read the MS blog article). Like lookup field information etc. It may also lead to both source and destination databases being corrupted! And it may possibly possibly make orphaned objects causing the failure to synch site messages in your event log. That in the end leads to outdated user profile information on site collections. You don’t want that.
So, the hot fix (read carefully, you will need two of them) seems to fix that issue. Just that you are aware of it!
Technorati Tags:
SharePoint
Check it out:Serve’s Sharepoint Blog
Answers Rating