|
jheavner-ce
-
2/29/2012 11:05:44 AM
Staging Sync failing
It's my understanding that synchronization uses GUIDS to ensure data integrity. However, I'm pretty sure that's not the case. I have a document on my development server with a NodeID of 709. When it synced to my staging server the NodeID became 620. Both documents have matching NodeGuid values. When I create a document under this document and attempt to sync, the sync fails and says the parent node doesn't exist and to please sync the parent node first. The parent node is there and the GUIDs match.
Just for fun I ran SQL Profiler to see what was happening. Here's the first applicable capture that demonstrates it's using NodeIDs and not the NodeGUID.
exec sp_executesql N'SELECT NodeAliasPath, NodeSiteID, NodeClassID FROM CMS_Tree WHERE [NodeID] = @ID',N'@ID int',@ID=993
Can someone please tell me what's going on here? This seems like a pretty significant bug. NodeID is an Identity. Those values are never going to be in sync unless it's a happy accident.
|