Selecting “SQL_Latin1_General_CP1_CI_AS” Collation in SQL Server

By xerocube | February 18, 2008

Recently, I have had to install a named instance of SQL Server 2005 along side a default instance of SQL Server 2000. The 2000 server had the following collation configured: SQL_Latin1_General_CP1_CI_AS. For testing purposes, we had to make sure the new instance had the same collation setting.

To ensure this, we selected the following during the installation process.

“Dictionary order, case-insensitive, for use with 1252 character set” with “Latin1_General”

I know this is just one-off information, but it may be useful to someone.

Topics: SQL | 26 Comments »

26 Responses to “Selecting “SQL_Latin1_General_CP1_CI_AS” Collation in SQL Server”

Elroy Says:
March 12th, 2008 at 3:04 am

Thank you so much. Your “just one-off” information has been usefull to someone – me;) .
You have just saved me from installing and uninstalling SQL Server until I got the correct SQL Collation settings.
So thanx again

Laszlo Says:
September 18th, 2009 at 2:09 pm

This info was really useful for me too.

Steve Says:
October 15th, 2009 at 8:25 am

Again, very helpful. I’ve been trying, without much success, to find this specific information elsewhere.

Jay Says:
February 22nd, 2010 at 1:13 pm

THANK YOU!! Glad you posted it, was very helpful to me also

Petri Says:
June 21st, 2010 at 9:04 pm

Thank you. Essential information that is easy to find in your blog is “REALLY” useful. I struggled to find this info in MSDN. Thanks.

Alex Says:
September 29th, 2010 at 1:10 pm

Hello man,
Thanks by information, help me very much.

Bye, Alex

Magnus Says:
October 12th, 2010 at 9:59 am

Thank you! Thank you! Thank you!

Saved me a lot of trial-and-error.

Thank God for Google and thank God for your post.

Bee Says:
May 26th, 2011 at 4:09 am

Thanks for the “one-off information”, after installing and uninstalling three times, I happened to see this blog, and my problem was sloved. Thanks for you help.

Vince Says:
June 17th, 2011 at 2:19 am

Thanks for the info, invaluable piece of information.

FUSE Says:
July 31st, 2011 at 7:49 am

Great lookout! – invaluable information. After installing and uninstalling multiple times I came across this blog and my woes are finish. I must say I learned alot about collation with the reading that I did.

Mark Says:
November 2nd, 2011 at 8:32 am

You’re great. many posts talking of this looks complicated, and more over I don’t see why the setup wizard doesn’t show the collation name in the same way…
you gave response in one line, so I thank you very much

Mike Says:
December 13th, 2011 at 10:46 pm

Thanks from me as well. Appreciate the help on collation.

Tom Says:
March 15th, 2012 at 6:21 am

Thanks again. It looks like this one-off information has been very useful to many!! Kind regards.

ddune Says:
August 14th, 2012 at 5:57 pm


Paul Says:
November 23rd, 2012 at 7:23 am

Perfect – exactly what I needed to know! Thanks!

fbizzle Says:
November 29th, 2012 at 11:29 am

tx though I needed CS instead of CI, i got what I needed here.

Vikash Says:
March 21st, 2013 at 3:37 am

Thanks a ton…U saved my day.

richy Says:
June 24th, 2013 at 7:30 am

brilliant. Thank you very much

Vance Says:
August 28th, 2013 at 6:47 am

Even though SQL 2008, 2008R2, and SQL 2012 have been available for the general public for a while, and SQL 2014 just around the corner, there are still instances where individuals are installing SQL 2005 on updated hardware (i.e., Windows 2008 R2).

As the other users noted above, thank you for your post. I can never remember the installer “description” version the description shown in SQL Server Management Studio.

ShamanNL Says:
September 21st, 2013 at 8:23 am

Fantastic!! This is exactly what I was looking for. 🙂

MBS Says:
September 25th, 2013 at 8:39 pm

I have to build a 2005 cluster with SQL_Latin1_General_CP1_CI_AS.
I only have option – Dictionary order, case-insensitive, for use with 1252 character set.
No mention of “with “Latin1_General”.

If I select – Dictionary order, case-insensitive, for use with 1252 character set.
Do I get SQL_Latin1_General_CP1_CI_AS?

Faiz Says:
June 26th, 2014 at 4:35 am

Thanks for the info, it saved lot of effort.

Michelle C Says:
August 4th, 2014 at 4:00 am

This is very helpful indeed. Thanks very much.

Krittaya Says:
September 3rd, 2014 at 9:17 pm

Thankyou so much!!! you safe my life.

Alin Says:
July 20th, 2015 at 10:02 am

yes, if you choose: Dictionary order, case-insensitive, for use with 1252 character set, then you’ll get SQL_Latin1_General_CP1_CI_AS.

User Says:
September 18th, 2015 at 9:55 am

Thanks, work for me.