Solved

If Latin1_General_CI_AS same as Latin1_General_CP1_CI_AS

Posted on 2010-08-27
2
4,726 Views
Last Modified: 2012-05-10
Hi;

In my SQL2000 server, my database is using Latin1_General_CP1_CI_AS collation.  Now, I need move/restore this db from SQL2000 to my new SQL2005 64 bit server, however; when I setup this new SQL2005 server, I only found the Latin1_General_CI_AS collation.  Can someone tell me are they the same?  Or, how can I find the Latin1_General_CP1_CI_AS in SL2005.

thanks!
0
Comment
Question by:KANEWONG
2 Comments
 
LVL 58

Accepted Solution

by:
cyberkiwi earned 125 total points
ID: 33547009
They are not the same.  The first one (you probably left out "SQL_" is a SQL collation, a hangover from SQL Server 7.0.  From 2000 onwards, SQL Server started offering and using Windows code pages and collations.

See here for some discussion

http://www.developmentnow.com/g/118_2003_9_0_0_463267/how-to-change-collations-to-SQL-Latin1-General-CP1-CI-AS.htm

To use this SQL Server collation (such databases will not work with Reporting/Analysis services)

The option is there on the screen called "Collation Settings" when you install SQL Server. Choose "SQL collations", "Dictionary order, case-insensitive, for use with 1252 Character set.".
0
 
LVL 4

Assisted Solution

by:pbarry1
pbarry1 earned 125 total points
ID: 33547172
Hi,

it looks like you're using a "SQL" collation on your SQL2000 Server (SQL_Latin1_General_CP1_CI_AS).  If you want to keep this exact same collation while installing your SQL 2005 Server, you need to select the "SQL Collations" option on the "Collation Settings" installation screen.  And then select the one corresponding to SQL_Latin1_General_CP1_CI_AS (run "sp_helpsort" on your SQL 2000 Server.  It will show the details on what to use).

But to answer your question: no, these two collations are not identical.  There are slight differences between the two:

1) Latin1_General_CI_AS:  
    Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive

2) SQL_Latin1_General_CP1_CI_AS:
    Latin1-General, case-insensitive, accent-sensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order 52 on Code Page 1252 for non-Unicode Data

Hope this helps.
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

There are some very powerful Data Management Views (DMV's) introduced with SQL 2005. The two in particular that we are going to discuss are sys.dm_db_index_usage_stats and sys.dm_db_index_operational_stats.   Recently, I was involved in a discu…
In this article we will discuss some EI Capitan Mail app issues and provide some manual process to resolve them.
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…
In a recent question (https://www.experts-exchange.com/questions/29004105/Run-AutoHotkey-script-directly-from-Notepad.html) here at Experts Exchange, a member asked how to run an AutoHotkey script (.AHK) directly from Notepad++ (aka NPP). This video…

856 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question