What does it mean by the As in the default collation SQL_Latin1_General_CP1_CI_AS?
The COLLATE {collation_name} clause of the CREATE DATABASE statement specifies the default Collation of the Database, and not the Server; Database-level and Server-level default Collations control different things.
What code page is SQL_Latin1_General_CP1_CI_AS?
For example, for the OS locale “English (United States)” (code page 1252), the default collation during setup is SQL_Latin1_General_CP1_CI_AS, and it can be changed to its closest Windows collation counterpart, Latin1_General_100_CI_AS_SC.
What’s the difference between latin1 and latin1 general?
The database’s default collation is Latin_General_BIN. So we need to have some observable difference between those two databases, write a test using comparing/ordering and assert the correct outcome (which should be compared/ordered by Latin1_General_CI_AS ).
Why is SQL _ latin1 _ general _ CP1 _ Ci _ as different?
For example, if we run the following SQL batch. Cannot resolve the collation conflict between “SQL_Latin1_General_CP1_CI_AS” and “Latin1_General_CI_AS” in the equal to operation. Which is caused by the join condition trying to compare string values where the collation is different on each side of the operator.
Where does collation SQL _ latin1 _ general…come from?
That is interesting; on MyTable1 the table with a varchar column using collation Latin1_General_CI_AS collation SQL is doing an implicit conversion during the lookup. Where has this implicit conversion come from? Well, it is caused by the collation of the database that I am running the query against.
What’s the difference between CI _ bin and Ci _ as?
_BIN will order in the binary (ASCII order) of characters while CI_AS will use dictionary order with case insensitivity and accent sensitivity so BIN will treat “A” and “a” as different characters and order them accordingly and sort the alphabet in this order. The catalogue table sys.columns shows the collation for each character-based column.