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

Ignored Differences

Top  Previous  Next

Normally, if there is any difference in a schema object (so it is indicated by color as shown here), it is propagated all the way to the root node.  In the sample shown in the previous topic, changes are in particular tables, but both the "Tables" collection node and the root node are also marked as changed.  This means you can select any of these nodes and get all the differences scripted.

This isn't always the desired behaviour, though. For example, "users" are likely to be different on your test server and on the production one and you probably won't want the Diff to try synchronizing them among the other changes.  So, starting from version 1.95, the Diff can stop propagation of certain changes up the tree, treating them as "minor differences".  If you set the "Don't script users/groups from the schema level" option, the users will still be compared, but any changes will stop at the "Users" collection node: when you select the root node, no users will be scripted.  To script the differences, you will have to select the "Users" node or a particular user(s).

diff_ignored_nodesConsider the following picture. It shows that there is no differences on the database level, although clearly there are changes under both "Users" and "Permissions" nodes. This is because in this case the Diff has been configured to ignore both.

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