Comments
Sort by recent activity
I've tried the binary collation and it has successfully identified the recalcitrant row as being the same in both DB. I then rechecked with the binary collation off and the row reappeared as being different.
The key is entirely in Capitals. Why should the case-sensitive comparison identify the two rows as the same whereas the case-insensitive comparison says they're different?
:?
David / comments
I've tried the binary collation and it has successfully identified the recalcitrant row as being the same in both DB. I then rechecked with the binary collation off and the row reappeared as being...
Richard,
I can send you the table in question directly for analysis purposes but I can't post it on a public site. So if we can arrange it privately I can send it to you.
However, looking at the options again I also tried the compare using the trim trailing spaces option and this had the same effect has the collation option. That is, with the option selected the rows appear as different! I have reviewed data and the two rows in question are identical, including the number of spaces.
I'm not getting any less confused with this! :? :?
David / comments
Richard,
I can send you the table in question directly for analysis purposes but I can't post it on a public site. So if we can arrange it privately I can send it to you.
However, looking at the o...
Thanks for your reply.
I am using the GUI and there is no warning that the index is not unique and there are no identity columns in this table. In fact, it is defined as a CLUSTERED UNIQUE primary key and there are no other indices!
On a test environment I have applied the changes and then reran the comparison and now I have this one row appearing as only in left DB and only in right DB, yet the contents of the rows is the same!
Any ideas?
thanks
David / comments
Thanks for your reply.
I am using the GUI and there is no warning that the index is not unique and there are no identity columns in this table. In fact, it is defined as a CLUSTERED UNIQUE primary...
The comparison key types in order are:
Char( 10 )
Char( 10 )
Varchar( 10 )
Varchar( 10 )
Varchar( 8 )
and the collation is SQL_Latin1_General_CP1_CI_AS across the board.
I will retry the compare with binary collation. / comments
The comparison key types in order are:
Char( 10 )
Char( 10 )
Varchar( 10 )
Varchar( 10 )
Varchar( 8 )
and the collation is SQL_Latin1_General_CP1_CI_AS across the board.
I will retry the compare wi...