Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Administration (2000)
 Problem in Collation

Author  Topic 

CSK
Constraint Violating Yak Guru

489 Posts

Posted - 2008-02-27 : 10:20:28
Gurus,

I have a problem in collation. One of our production database is in Chineese collation.(Chinese_PRC_CI_AS) But master model..and rest of the other database is in SQL_Latin1_General_CP1_CI_AS. Its very urgent to change the chineese collation to SQL_Latin1_General_CP1_CI_AS.


Please anyone help me to start production again.

Thanks
Krishna

AndrewMurphy
Master Smack Fu Yak Hacker

2916 Posts

Posted - 2008-02-27 : 10:28:09
I think you are looking at a DTS/ BCP/ ISQL job to transfer the data into a new database which has the correct collation. Changing database collation now, will only effect future columns added. Changing column collation will (I believe) only effect future rows added.
Go to Top of Page

CSK
Constraint Violating Yak Guru

489 Posts

Posted - 2008-02-27 : 10:31:28
No i am using linked server. this is fropm 2000 to 2005. I cant transfer from 2000 to 2005
2000 having Chineese Collation and 2005 having latiin collation. how to resolve it.

This is the error message i got it

System.Data.SqlClient.SqlException, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

Message : Cannot resolve the collation conflict between "Chinese_PRC_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.

Go to Top of Page

CSK
Constraint Violating Yak Guru

489 Posts

Posted - 2008-02-27 : 11:08:31
Solved-> I have added the collation in all where class

Thanks
Go to Top of Page

AndrewMurphy
Master Smack Fu Yak Hacker

2916 Posts

Posted - 2008-02-27 : 11:38:06
But that's not converting your actual data.....your underlying chinese data is still saved with a chinese collation. All it means is that any queries you are running across 2 databases are passed through a collation filter to make them "equivalent (or equal)".....and that filter may have a performance cost...but the cost may be soo small not to worry about.
Go to Top of Page

CSK
Constraint Violating Yak Guru

489 Posts

Posted - 2008-02-27 : 11:45:03
Yeah, But this is for only 10 stored procedures. That is wat i have included collation in all the where class.

Thanks for the suggession
Krishna
Go to Top of Page
   

- Advertisement -