SQL Data Compare - 9.0
Options used in the command line
You can set project configuration options by using the /Options switch.
For example, when mapping objects, SQL Data Compare considers underscores in object names to be differences by default. Therefore, if the objects [dbo].[Widget_Prices] and [dbo].[WidgetPrices] were identical, they would not be mapped, and so could not be compared. To successfully compare these objects, use:
/Options:IgnoreUnderscores
SQL Data Compare now treats those objects as identical, and they can be compared.
To specify multiple options, separate the options using commas:
/Options:<option1>,<option2>,<option3>
If you do not explicitly set any options, the defaults are used. See Defaults below.
Note that there are changes to the command line syntax of SQL Data Compare in version 8. The names, aliases, and behaviour of some switches and options is different to that of earlier versions.
For more information, see Changes to the command line in SQL Data Compare 8
Defaults
If you do not specify any options, the following default options apply:
- IgnoreSpaces
- IncludeTimestamps
- IncludeIdentities
- DisableKeys
- OutputComments
- ReseedIdentity
- (IgnoreCase) - This option is deprecated, and case insensitive comparison is now the default behaviour.
If you want to use these defaults with additional options, specify the default argument and the additional options. For example:
/Options:Default,TrimTrailingSpaces,CompressTemporaryFiles
If you do not specify the default argument, only the options you explicitly specify apply.
To specify no options, use the none argument.
Further options are detailed below.
CaseSensitiveObjectDefinition
Alias: cs
Treats object definitions as case sensitive when mapping. For example, Table_A and table_a would not be mapped automatically.
CompressTemporaryFiles
Alias: ctf
Compresses the temporary files that SQL Data Compare generates while performing the comparison. This makes it less likely that you will run out of disk space when comparing very large databases.
Default
Alias: d
Applies the default options.
DisableAndReenableDDLTriggers
Alias: drd
DDL triggers can cause problems when you run the synchronization. Select this option to disable any enabled DDL triggers before synchronizing the databases, and re-enable those triggers following synchronization.
DisableAndReenableDMLTriggers
Alias: t
Disables DML triggers on tables and views before synchronizing the databases, and then re-enables those triggers following synchronization.
DisableKeys
Alias: k
Disables foreign keys before synchronizing the databases, and then re-enables those foreign keys following synchronization. Note that in some circumstances foreign keys will be dropped and re-created rather than disabled and re-enabled.
DoNotOutputCommentHeader
Alias: nc
When this option is selected, comment headers are not included in the output script.
DropConstraintsAndIndexes
Alias: c
Drops primary keys, indexes, and unique constraints before synchronizing the databases, then re-creates them following the synchronization.
If the primary key, index, or unique constraint is the comparison key, it cannot be dropped.
ForceBinaryCollation
Alias: fbc
Forces binary collation for all string data types, irrespective of column collation, resulting in a case-sensitive comparison. When this option is selected and the comparison key is a string, this may result in slower performance because the indexes are not used.
ForceCheck
New option. Forces any constraints (for example, those on foreign keys) disabled by SQL Data Compare to be re-enabled with CHECK.
IgnoreCase
This option is deprecated, and case insensitive comparison is now the default behaviour.
IgnoreSpaces
Alias: is
When mapping objects for comparison, spaces in the names of objects are considered by default. This option ignores spaces in the names of objects, enabling them to be mapped. For example [dbo].[Widget Prices] is mapped to [dbo].[WidgetPrices].
IgnoreUnderscores
Alias: iun
When mapping objects for comparison, underscores in the names of objects are considered by default. This option ignores underscores in the names of objects, enabling them to be mapped. For example, [dbo].[Widget_Prices] is mapped to [dbo].[WidgetPrices].
IncludeIdentities
Alias: iid
Includes identity columns in the comparison.
Note that you cannot synchronize a view if it includes an identity column.
IncludeIndexedViews
Alias: v
Includes views in the comparison. Views can be synchronized only if the referenced rows are from a single table, and the referenced columns are simple. For example, they must not include identity columns or computed columns.
IncludeTimestamps
Alias: its
Includes timestamp columns in the comparison.
Note that timestamp columns cannot be synchronized.
None
Alias: n
To specify no options, use the none argument.
OutputComments
Alias: oc
Includes comments in the synchronization SQL script.
ReSeedIdentity
Alias: rsi
Re-seeds identity columns so that identity values in the database you are updating match values in the source database.
TransportCLRBinary
Alias: tclr
When this option is selected, SQL Data Compare uses the binary representation of CLR types in the synchronization SQL script. If this option is not selected, CLR data types are represented as strings.
TrimTrailingSpaces
Alias: tts
When this option is selected, and the data in two columns differs only by the number of spaces at the end of the string, SQL Data Compare treats those columns as identical.
Note that this option does not apply to CLR columns, or XML columns.
UseChecksumComparison
Alias: ucc
When this option is selected, SQL Data Compare performs a checksum prior to comparison. Data is compared only if the checksums differ. You can use this option to improve the performance of SQL Data Compare.
Note that in SQL Server 2000 databases, db_owner permissions are required to use this option.
UseTransactions
Alias: ut
When this option is selected transactions are used in the synchronization SQL scripts, enabling changes to be rolled back if the synchronization fails. BEGIN TRANSACTION is inserted at the beginning of the synchronization SQL script, and COMMIT TRANSACTION at the end of the script.
See also |
Was this article helpful?
Using SQL Data CompareSQL Data Compare
- Logging and log files
- Internal Connection Fatal Error in versions 4 and 5
- NULL textptr passed to UPDATETEXT function when running synchronization
- How much free hard disk space is required?
- Comparing the data of two tables in the same database
- Suggestions to combat comparison and synchronization performance issues
- SQL comparison and synchronization automation capabilities
- SqlNullValueException occurring in synchronization wizard
- SQL Data Compare command-line XML argument file examples
- Using Windows authentication logons between domains
- Using a filter on a column on related (joined) tables
- Determining minimum database permissions for SQL Data Compare
- Tables with compound keys may not be mapped automatically
- Best practices for synchronizing data
- Cleaning up a SQL script after SQL Compare or SQL Data Compare
- Troubleshooting System.OutOfMemoryException during comparison
- Exception thrown by db reader 1
- Reseed applying "incorrect" identity values
- Running migration scripts using SqlCmd.exe
- This SQL Server has been optimized for x concurrent queries.
- SQL Data Compare showing differences in 2 identical databases
- How to force SQL Compare and SQL Data Compare to use an Encrypted Connection
- Improving the performance of SQL Data Compare
- Logging and log files
- Case-sensitive comparisons
- Tables or views that could not be compared
all SQL products
- Compatibility of Red Gate tools in 64-bit environments
- Application has encountered an error and needs to close
- Error message after installing SQL Toolbelt - The description for Event ID ( 1 ) in Source ( nview_info ) cannot be found.
- Changing the temporary directory used by the installer
- Toolbelt Installer "hanging" while "scanning volumes"
- Login failing with "trusted SQL Server connection" error when using RunAs
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SQL Data Compare
- Activating your products
- Activating your products
- Getting help offline
- Getting better performance out of SQL Data Compare
- Release notes - version 10.xx
- SQL Data Compare release notes - version 7.xx
- SQL Data Compare release notes - version 8xx
- SQL Data Compare release notes - version 9.xx
all SQL products
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs
