Character encoding woes

lunadesign

I'm comparing two SQL Server databases. I've got a varchar field that has extended characters (like the degree symbol) that consistently get messed up by SQL Data Compare (but work fine in SSIS). Is there a setting somewhere that I'm missing?

Thanks in advance!

lunadesign

I've been doing some digging and discovered one interesting tidbit: the source database uses the SQL_Latin1_General_CP850_BIN2 collation while all of my destination databases use the SQL_Latin1_General_CP1_CI_AS.

So I think the trick is finding some way to get SQL Data Compare or SQL Server to do the code page conversion. Somehow SSIS is doing this without me using any CAST or CONVERT functions. I can't figure out how this with SQL Data Compare.

Brian Donahue

Can you please let us know the situation where the Unicode characters are causing the problem? For instance:

• The results displayed are not showing the character properly
• The comparison result is wrong (data should be equal, but DC says it's different)
• The syncrhonization script does not display properly (in SSMS, Notepad?)
• The synchronization script will not run on the SQL Server

Thanks!