Contents 

AdeptSQL Diff Reference
AdeptSQl Diff versions, history and milestones
Supported versions of MS SQL Server
Getting started
Connecting to databases
Scanning available servers
Saving and opening comparisons
Running from command line
Diff in portable mode
Working with the schema
Viewing schema differences
Ignored Differences
Comparing objects side-by-side
Dragging and dropping schema items
Using schema filters
Generating comparison reports
Customizing the reports
Executing the SQL
SQL errors and warnings
Transaction support
Keyboard shortcuts
Editing commands and keyboard shortcuts
Using keyboard templates
Choosing debugger's key mapping
Comparing table data
DataDiff overview
DataDiff configuration dialog - table-level
DataDiff configuration dialog - columns
Special situations comparing data
Exporting data to Excel
DataDiff Reports
Column configuration file
Configuring AdeptSQL Diff
Options dialog
Schema Scan
Selective Loading
Comparison
Name Comparison
Code Comparison
User-defined types
Indexes and Statistics
Permissions and XProps
Synonyms
Other details to ignore
Scripting
General logic
Side-by-side scripting
Formatting
Identifiers
Schema Level
Tables
Constraints
Default Values
Procedures, Views, etc
Visuals
Text Fonts
Schema Tree
Summary collections
Side-by-Side View
Suppressed dialogs
Data comparison options
General
Scripting
Column Config File
Using COM Automation interface
Automating schema comparison
Automating data comparison
Licensing and contact info
Registration of AdeptSQL Diff
License conditions
Contact information

AdeptSQL Diff Online Help

Prev Page Next Page

Options / Comparison / Details to ignore

Top  Previous  Next

opt_IgnoredDetails1Options 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 scripts.

Ignore 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 anyway.

Ignore 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.

Ignore 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.

Ignore COLLATE. The collation order for character columns and for the entire database will not be compared or scripted.

Bound 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.

Ignore 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 the sp_settriggerorder stored procedure.  Depending on this setting, the Diff can either compare/synchronize or ignore the trigger order.

   
Converted from CHM to HTML with chm2web Standard 2.85 (unicode)