Re: SQL_Latin1_General_CP1_CS_AS

Nasir (nmajeed@xxxxxxxxxx) writes:
When installing SQL server default is 'dictionary order
case-insensitve..1250..', however I chose dictionary order
case-SENSITIVE from the SQL collation. At the top window there
are'Latin1_General' with the option of case-sensitive, where you also
see BINARY etc...

Is there any difference between SQL_Latin1_General_CP1_CS_AS select
from lower window and 'Latin1_General' select with case-sensitive from
the upper window?

Yes, there are differences. One is an SQL collation, the other is a
Windows collation.

SQL Collations are SQL Server's own collations and represent a legacy
from the time, when SQL Server defined its sort orders on its own.
Windows collations on the other hand are taken from Windows.

When you install SQL Server, you will be suggested a default collation
depending on the system locale. I believe that for most settings you will
be suggested a Windows collations. For instance, in my case, I am
proposed Finnish_Swedishå_CI_AS (which I promptly change to CS_AS). But
there is at least one exception: if your system locale is US English,
you will be suggested SQL_Latin1_General_CP1_CI_AS.

So what is the difference then? Ehum, I will have to admit that I am a
little foggy on the details, but the difference is mainly in how
punctuation characters and digits are sorted.

I would recommend using a Windows collation.

--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.

Relevant Pages

  • Re: Login failed for user (null)
    ... Not associated with a trusted SQL Server connection. ... However, if you deal with the Domain controller, most of the controls there ... > (Windows 2003 server, domain member). ...
    (microsoft.public.inetserver.asp.db)
  • Re: Login failed for user (null)
    ... Not associated with a trusted SQL Server connection. ... However, if you deal with the Domain controller, most of the controls there ... > (Windows 2003 server, domain member). ...
    (microsoft.public.sqlserver.connect)
  • Re: Login failed for user (null)
    ... Not associated with a trusted SQL Server connection. ... However, if you deal with the Domain controller, most of the controls there ... > (Windows 2003 server, domain member). ...
    (microsoft.public.sqlserver.security)
  • Re: Login failed for user (null)
    ... Not associated with a trusted SQL Server connection. ... However, if you deal with the Domain controller, most of the controls there ... > (Windows 2003 server, domain member). ...
    (microsoft.public.inetserver.iis.security)
  • Re: Login failed for ServerGuest
    ... I think it is not a limitation in Windows 2000. ... access SQL server on Win2000 server by using Windows authenctication if I ... | I have noticed that when I try to log in using Windows Authentication ...
    (microsoft.public.sqlserver.connect)