How can we help you today? How can we help you today?
j.salmon
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
Hey Brian, Thanks for the response. Here's the /include help section from the SQL Data Compare command line help file version: 5.4.0.64 (accessed with the verbose and HTML options) /include:<object type>:<regular expression> Database objects or types to be included. Includes objects of the specified type whose identifiers match the specified regular expression. Note that /include and /exclude rules are applied in the order they are specified on the command line, or in the XML file containing the argument specification. If an object is matched by both an include and exclude rule then the exclude rule takes precedence. Note also that if an object has been explicitly included in the project file it will be included in the comparison even if no include rule matches it, unless it is excluded by an exclude rule. To include all objects of a type only specify the type (eg /include:View ) Value Alias Description All - All database objects. Table - Tables. View - Views. The last line specifically states that to include all objects of a certain type, that the you should type </include:table>. What is the correct syntax. Again, for a small database, listing all tables with includes would probably be fine. For any normal to large sized database, this isn't really a practical thing to do. Also, this creates a large amount of maintenance to have numerous developers remember to add the tables to the file and retest nightly builds, etc. [/b][/i][/quote] / comments
Hey Brian, Thanks for the response. Here's the /include help section from the SQL Data Compare command line help file version: 5.4.0.64 (accessed with the verbose and HTML options) /include:<o...
0 votes