New answers tagged

8

(The following copies portions of the first part of my answer to a related DBA.StackExchange Q&A: Why not use SQL_Latin1_General_CI_AS for a global system? and adds some additional information.) Collations in SQL Server, with respect to handling differences between various languages (meaning: this is not an all-inclusive list of what Collations do), ...


2

They're used to define the rules for storing non-unicode data, and sorting and comparing non-unicode data (including how to deal with case sensitivity. There's a server collation which is used for your system databases and for tempdb; that's kind of important if you're comparing data between servers, databases, or tempdb and your local database. Then ...


0

Maybe you can use CHARINDEX casting your Address1 to varbinary(8000) to identify the offending data: select * from [ForgeDB].[Snapshot].[SnapshotPersonEmployee] where charindex(0xA0, cast(Address1 as varbinary(8000))) > 0; Check this answer: http://dba.stackexchange.com/a/37355/55596



Top 50 recent answers are included