Different extended property order falsely reports difference
mgwiz
Posts: 6
Multiple table and associated trigger extended properties, though identical, are listed in different orders in side by side window, giving false differences.
This happens even if tables are identical, even though the table is listed in the identical objects group. This isn't really a problem as the tables are not listed as different.
However, if there is another difference, the table is listed in the different objects group and these false differences just muddy the water, making it difficult to identify the actual differences.
What exactly is the "extended property order" mentioned in another posting? Why aren't they listed in major_id/name order, or even just name/value order?
This happens even if tables are identical, even though the table is listed in the identical objects group. This isn't really a problem as the tables are not listed as different.
However, if there is another difference, the table is listed in the different objects group and these false differences just muddy the water, making it difficult to identify the actual differences.
What exactly is the "extended property order" mentioned in another posting? Why aren't they listed in major_id/name order, or even just name/value order?
Comments
I think the order that SQL Compare originally put extended properties in is the order they were created, or the order they're found in the system tables (which should be the same). By v6 this should be improved somewhat - if you're not using v6, could you get a trial version and tell us if the problems are happening in that version too?
Redgate Software
It's SQL Compare 6.1.0.53 .
http://www.red-gate.com/MessageBoard/viewtopic.php?t=6830
Product Manager
Redgate Software
If it's still a problem in 6.2.0.271 I'd like to see an example of the extended properties being out of order (a snapshot or backup or a script I could run to create such a database) so I can work out what's going wrong and hopefully get it fixed.
Redgate Software