Latin1_General_BIN Collation

  • I am installing SQL Server 2008 R2 Standard Edition with required SQL_Latin1_General_BIN collation, but this particular collation is not found in the available list of the software installer. However, SQL_Latin1_General_CP437_BIN and SQL_Latin1_General_CP850_BIN are available. Are these two collation types compatible with SQL_Latin1_General_BIN? Can someone advise me on how to get SQL_Latin1_General_BIN at SQL Server installation?

    Thank you for you help in advance.

  • Did you ever figure this out? I'm looking at the same thing and it looks like you need to select the Windows collation designator and sort order radio button, then Latin1_General with the Binary check box.

  • Jon.Morisi (11/20/2012)


    Did you ever figure this out? I'm looking at the same thing and it looks like you need to select the Windows collation designator and sort order radio button, then Latin1_General with the Binary check box.

    This is correct. Just curious, is there a reason you need the Latin1_General_BIN collation? I have nothing against it, just curious why it is required.

  • Just setting up Vendor software that has the requirement. SharePoint uses a non-default collation as well.

    http://msdn.microsoft.com/en-us/library/ms188046.aspx

    http://www.sqlservercentral.com/Forums/Topic647177-146-1.aspx#bm647387

  • Jon.Morisi (11/20/2012)


    Just setting up Vendor software that has the requirement. SharePoint uses a non-default collation as well.

    http://msdn.microsoft.com/en-us/library/ms188046.aspx

    http://www.sqlservercentral.com/Forums/Topic647177-146-1.aspx#bm647387

    Yep, been there, done that.

    PeopleSoft requires using Latin1_General_BIN as its collation.

  • Choose Windows collation.

    Designer: Latin1_General

    Check Binary. All other options become invalid at that point.

  • Eric Humphrey (7/24/2014)


    Choose Windows collation.

    Designer: Latin1_General

    Check Binary. All other options become invalid at that point.

    I realize that you and I have just answered a 2 year post but I thought I'd also add my 2 cents.

    Make darned sure that you really want a case-sensitive server before you select a case-sensitive collation. I've found that there's actually very little that needs to be case sensitive in most U.S. application (can't speak to requirements of other countries). As a result, I'll select a case-insensitive collation for the server and only make the columns that require case-sensitivity to have a case-sensitive collation at table creation time. You have to be a little careful about how things are used in TempDB when you do that but it's a whole lot easier for a lot of everything else.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.


    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Old post but thought I'd add this for SQL 2014.

    In Collation Designator: Latin1_General

    Select Binary Checkbox

    Everything else will be greyed out.

    Will appear as Latin1_General_BIN

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply