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
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).
Consider 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.