Comments
2 comments
-
Granted wrote:I've got a database on two systems where I know I have differences between the two. On one machine I compared them with Version 5. On the other with Version 6. The version 6 machine is showing two problems, one a foriegn key that is different and a second foreign key that is missing. The version 5 machine is correctly identifying the difference as a single problem, the missing key.
The beta has missed the fact that the key it has identified as different is simply in a different order due to the key that is missing.
The really interesting thing is that there is another key on the table that version 6 correctly identifies as being the same.
This may seem unclear. Let me know. I've got screen captures.
SQL Compare internally does not care about the order of the foreign keys. In the side by side comparison window what you see is the creation SQL. The differences are shown as textual differences in the creation scripts, but this does not mean that the two foreign keys on the same line are paired up. They are displayed in the order SQL Server stores them. Can you try to create a synchronization script, and see if the foreign keys that seem to be different are actually modified?
I'll try to include a fix for ordering the foreign keys so that they are better matched in the textual comparison.
Regards,
Andras -
Thanks. You're right. It generated the correct script just fine. I'd still suggest making the change so that it behaves more like version 5 because it just makes for more clear behavior.
Add comment
Please sign in to leave a comment.
The beta has missed the fact that the key it has identified as different is simply in a different order due to the key that is missing.
The really interesting thing is that there is another key on the table that version 6 correctly identifies as being the same.
This may seem unclear. Let me know. I've got screen captures.