Options used when synchronizing databases.

Namespace:  RedGate.SQLDataCompare.Engine
Assembly:  RedGate.SQLDataCompare.Engine (in RedGate.SQLDataCompare.Engine.dll)

Syntax

Visual Basic (Declaration)
<FlagsAttribute> _
Public Enumeration SqlOptions
C#
[FlagsAttribute]
public enum SqlOptions
Visual C++
[FlagsAttribute]
public enum class SqlOptions

Members

Member nameDescription
Default

The default options when synchronizing databases. These are:

  • DisableKeys
  • OutputCommentHeader
  • UseTransactions
  • OutputComments
  • ReseedIdentity
None
None.
DisableTriggers
Disable, then re-enable, DML triggers on tables and views in the synchronization script.
DisableKeys
Disable, then re-enable, foreign keys in the synchronization script. Note that in some circumstances foreign keys are dropped and recreated rather than disabled and re-enabled.
DropConstraintsAndIndexes
Drop and recreate primary keys, indexes, and unique constraints in the synchronization script. If the primary key, index, or unique constraint is the comparison key, it cannot be dropped.
OutputCommentHeader
Include the comment header in the synchronization script. The comment header contains information about the databases that you are comparing, and the version of SQL Data Compare.
UseTransactions
Inserts BEGIN TRANSACTION at the beginning of the synchronization script and COMMIT TRANSACTION at the end of the synchronization script.
TransportCLRBinary
In the synchronization script, SQL Data Compare can use the binary representation or the string representation (.ToString()) of the CLR column. Setting this option forces SQL Data Compare to use the binary representation in the synchronization script. The binary representations of the CLR columns must be the same.
DDLTriggerDisable
Disable and then re-enable all DDL triggers in the synchronization script.
OutputComments
Include the comments in the output script. The comments make it easier to locate items in the output.
ReseedIdentity
Reseeds identity columns so that identity values in the database you are updating match values in the source database.

See Also