Comments
1 comment
-
Hi there,
The problem you are seeing is because of the two ways that SQL Compare compares objects. At the start of the comparison, or each time you refresh, the engine does a semantic comparison of all the objects in the data sources and stores these results in the top grid.
However, each time you select an object in the top grid the SQL Differences pane does a simple textual comparison of objects. This is done to improve performance and memory usage, and because 90% of textual differences are actually semantic differences too.
However, in some cases like the one you highlight, a textual difference isn't actually a semantic difference and the SQL Differences pane will highlight differences, when the top grid will report the object as identical. As we display most of these objects exactly as they are stored in the system catalogs we don't feel that we should alter them, and some of these differences may actually be of interest to users.
In the case that you highlight SQL Compare will display only report that the objects are different in the top grid if there is a different elsewhere in the objects. The ordering of triggers alone shouldn't cause the top grid to be report a difference. If it has then you have found an issue. If you can forward me the schema of the effected objects I will take a look and see what we can do about it.
We are going to have to look into improving the SQL Differences pane difference matching in future releases, but this won't be changed in the initial point release. Sorry.
Jonathan
Add comment
Please sign in to leave a comment.
But the triggers were created in a different order on the source and target tables.
SQL Compare 6 beta reports:
Trigger 1 as new on source table
Trigger 2 as identical on source and target table
Trigger 1 as new on target table.
On the Source table the triggers were created in the following order.
1. trigger 1
2. trigger 2
On the Target table the triggers were created in the following order.
1. trigger 2
2. trigger 1