08-01-2013 04:27 AM
Looking for suggestions to recover changes trapped in a remote 2013 Premium HF3 database after the sync failed.
"Message: Synchronization has failed. Cannot insert duplicate key row in object 'sys.syscommittab' with unique index 'si_xdes_id'. The duplicate key value is (222664). Failed to flush the commit table to disk in dbid 7 due to error 2601."
The remote was using the scheduler to sync data for a couple of states. 3 other RDB users are synching OK. Would have been nice to have some "in your face" indication of sync failure with the sync process was on autopilot.
My thought is to delete the affected states in the master database, move a copy of the RDB to the server and then import.
Any pitfalls in this approach?
08-01-2013 04:44 AM
Shoot, Ready, Aim!
Found http://kb.sagesoftwareonline.com/app/answers/detail/a_id/28141 which describes the problem is caused by an error associated with Microsoft® SQL Server® 2008 R2.
Solution: Apply Service Pack 1 for SQL Server 2008 R2 & then run the batch file provided.
Do I glean from this that all 2013 installs that may sync should be followed up with SQL SP1 to prevent this error?
08-01-2013 07:30 AM