How can we help you today? How can we help you today?
j.salmon
AndrewRMClarke wrote: C'mon! lets have the feature back in. It really is time to do something nice with snippets. Ditto - add this back in. / comments
AndrewRMClarke wrote: C'mon! lets have the feature back in. It really is time to do something nice with snippets. Ditto - add this back in.
0 votes
Ok, following your instructions........here's what I did. I ran the following sqldatacompare.exe /project:"c:\VinylRemake.sdc" /include:Table:\[VinylRemakeHistory\] This runs the data compare only for the table VinylRemakeHistory. This runs quickly and outputs the results as expect. Registering databases Mapping Comparing databases Finished Summary Information ===================================================================================================================================================================================================================================== DB1 = DB2 = alsddb4.aldata002 Object type Name Records DB1 DB2 Table [dbo].[VinylRemakeHistory] 10 >> Table [dbo].[VinylRemakeHistory] 52960 << If I add a sync to the end of the previous cmd: sqldatacompare.exe /project:"c:\VinylRemake.sdc" /include:Table:\[VinylRemakeHistory\] /sync The sync. fails. I get the following error: Error: Synchronization of 'Server1.TestDB1' and 'Server1.TestDB2' failed: The DELETE statement conflicted with the REFERENCE constraint "FK_VinylRemakeHistoryProductionLine_VinylRemakeHistory". The conflict occurred in database "TestDB2", table "dbo.VinylRemakeHistoryProductionLine", column 'VinylRemakeHistoryID'. In the project, I have specified for it to drop everything in the sync behavior (foreign keys, prim keys, triggers, etc). If I reopen the .sdc in data compare, the settings are retained, but they don't appear to be used with the command line compare? / comments
Ok, following your instructions........here's what I did. I ran the following sqldatacompare.exe /project:"c:\VinylRemake.sdc" /include:Table:\[VinylRemakeHistory\] This runs the data compare only ...
0 votes
I got this handled by using the NoSQLPlumbing option in the argfile. The errors returned by sql compare are a little confusing since it is referencing a linked server on the dest server. Jon / comments
I got this handled by using the NoSQLPlumbing option in the argfile. The errors returned by sql compare are a little confusing since it is referencing a linked server on the dest server. Jon
0 votes