Options on this page make
certain object properties to be ignored during comparison
(differences in these properties will not be displayed in the
schema tree) and not scripted in either CREATE or ALTER
FILEGROUP clause. If you check this
option, the Diff would never script ON FILEGROUP clause for tables
and indexes, and neither it will script filegroup definitions on
the database level (ALTER DATABASE ADD FILEGROUP...). Note that
regadless of this flag, the Diff never scripts ON FILEGROUP for
tables and indexes which are on the default filegroup
FILLFACTOR, PAD_INDEX attributes. These options are
checked by default, which means the Diff would not consider changes
in the FILLFACTOR/PAD_INDEX as differences and wouldn't script
"WITH FILLFACTOR=..." for indexes and constraints.
NOT FOR REPLICATION. The NFR flag in
IDENTITY columns, constraints and triggers will be ignored on
comparison. When synchronizing a changed object, the Diff will keep
its original NFR flag, if possible.
COLLATE. The collation order for
character columns and for the entire database will not be compared
DEFAULT/RULE vs. equivalent constraints. In MS SQL,
default values and validity checks for table columns can be
specified either by regular DEFAULT/CHECK constraints, or by
binding a global DEFAULT/RULE object to the column. By
checking one or both of the "[x] Only compare the actual
expression" options, you can tell the Diff that as long as the
checked or default expression is the same, the way it is specified
is irrelevant and should not be displayed as a difference.
trigger order (since Diff 1.98).
MS SQL Server allows to specify execution order when multiple
"AFTER" triggers are defined for the same operation. One trigger
may be defined to run first, one to run last and any other triggers
will run between the "first" and the "last" in unspecified
order. In the script, the trigger order is specified using
procedure. Depending on this setting, the Diff can either
compare/synchronize or ignore the trigger order.