SQL Server’s Binary Collations

   Today, I will
discuss SQL Server’s Binary collations. 
In SQL Server, we have two kinds of binary collations: BIN collation,
which has collation name ending with _BIN and BIN2 collation, which has
collation name ending with _BIN2.  In SQL
Server, a string value (either varchar or nvarchar value) is encoded and stored
as a sequence of binaries.  For nvarchar
value, we always use the UCS-2 encoding. 
For varchar value, we use the codepage of corresponding collation
associated with the value. 

    For “Binary” collation, we use a sorting
algorithm based on the binary sequence of the string to sort the string data. Now,
let us look the binary sorting algorithm. 
For varchar type, the algorithm is quite simple; the sorting result of a
set of varchar values with binary collation is the same as we sort them use the
binary sequence.  In T-SQL syntax:

            Select *
from T order by varcharC 

Equals to

            Select *
from T order by convert(varbinary(8000), varcharC) 

Note, it is always true for both BIN collation and BIN2

     Now, let us look
at sorting the nvarchar values.  In this
case, we can not sort them purely use the binary sequence, the reason is that
the binary sequence represents a sequence of UCS-2 characters, which take two
byte per character.  Because SQL Server
internally uses Little-Endian to store the UCS-2 character, the binary sorting
may result undesired result.   For
example, character a (We usually use U+0061 to indicate its Unicode Code Point
assigned by Unicode Org) is encoded as 0x6100 in SQL Server, so If we sort
these characters in their binary sequence order,  we will not be able to get a Unicode Code
Point ordered sorting result  which is  desired for many application.  In SQL Server’s BIN2 collation, we sort the
nvarchar type according to their Unicode Code Points instead of the binary
sequence (internally, we do comparison per WCHAR based, which is 2 bytes).  Now, comes the BIN Collation, the algorithm
is wired.  It first compares two characters
based on the first WCHAR values of the two characters, if the values are equal,
the algorithm will do binary based comparison for the reminding binary sequences,
i.e., byte per byte comparison.

     Hope your guys
can follow my writing.  If not, you can
simply assume that BIN2 is a Unicode Code Point based sorting algorithm, and it
is desired by many customer. But BIN is not.

From the sorting algorithm’s view,
all BIN collation use the same algorithm and all binary2 collation use another
algorithm.  Then why we have
latin1_general_bin or Japanese_bin collation? 
The reason is that they use different code page for encoding the
characters sorting in the varchar type.  A
Latin1_General_Bin collation can not hold any Japanese collation, so even they
use the same algorithm to sort the data, but people still need to choose the
language which the data will stored, such as English, Chinese, Japanese
etc.  Note, this only apply to varchar
data type.  For nvarchar data types,
these collations have no difference at all.

     On the other
hand, SQL Server has many linguistic collations which sort string linguistically
using the language associated with the collation.  All collations which are not binary collation
are linguistic collations.  For example,
Latin1_General_CI_AS is a linguistic collation; it uses a sorting algorithm
compatible with several of English language and many Western European languages.  Please don’t confuse with the name of
Latin1_General, it actually can sort all Unicode characters defined in Unicode
3.2 characters and it can also sort many other languages correctly as well (if
the language has no sorting conflict with the latin1_general sorting rule).  I will start another article to describe the linguistic
collation in deep details.

    As a conclusion, binary collations have
better performance than linguistic collations, and that is the main advantage
of using a binary collation. A binary collation is always case sensitive and
assent sensitive. User should try use BIN2 collation instead of BIN collation.

Comments (2)

  1. Marcin Zawadzki says:

    Thanks for clearing.

    BOL information about BIN and BIN2 difference is unclear.

  2. JVacha says:

    With _bin collation, only "SPACE" character, i.e. DEC# 32 is at first position, otherwise it is all the same.


    create table a (

     i bigint not null primary key,

     x nvarchar(10) collate japanese_bin,

     y nvarchar(10) collate czech_bin2



    — insert 0x0000 to 0xFFFF characters

    declare @x bigint;

    set @x = 0;

    while @x < 65536 begin

    insert into a (i, x,y) values (@x, nchar(@x), nchar(@x));

    set @x = @x + 1;



    — sort by x and y

    select identity(bigint, 0,1) as id_bin, i as i_bin, x as x_bin, y as y_bin into vysl1 from a order by x;

    select identity(bigint, 0,1) as id_bin2, i as i_bin2, x as x_bin2, y as y_bin2 into vysl2 from a order by y;


    — difference

    select id_bin, i_bin, i_bin2 from vysl1 inner join vysl2 on vysl2.id_bin2 = vysl1.id_bin where vysl1.i_bin != vysl2.i_bin2 order by vysl1.id_bin;



    id_bin               i_bin                i_bin2

    ——————– ——————– ——————–

    0                    32                   0

    1                    0                    1

    2                    1                    2

    3                    2                    3

    4                    3                    4

    5                    4                    5

    6                    5                    6

    7                    6                    7

    8                    7                    8

    9                    8                    9

    10                   9                    10

    11                   10                   11

    12                   11                   12

    13                   12                   13

    14                   13                   14

    15                   14                   15

    16                   15                   16

    17                   16                   17

    18                   17                   18

    19                   18                   19

    20                   19                   20

    21                   20                   21

    22                   21                   22

    23                   22                   23

    24                   23                   24

    25                   24                   25

    26                   25                   26

    27                   26                   27

    28                   27                   28

    29                   28                   29

    30                   29                   30

    31                   30                   31

    32                   31                   32

    Tested on SQL Server 2012.

Skip to main content