January 21, 2008 at 9:54 am
Hi All,
I am currently testing migrating a database from SQL 7 to SQL 2005.
Following a backup/copy/restore to the new server, the database now has a backwards compatibilty collation of SQL_Latin1_General_CP1_CI_AS.
I have changed the database itself to be Latin1_General_CI_AS but (as expected) the collation at a column level remains SQL_Latin1_General_CP1_CI_AS, so this needs changing.
I found a nifty script on this website (LM_ChangeCollation) which uses a cursor to go through all the tables and do a Alter Table Alter Column Collate.
Genius!
Except it doesn't work 🙁
It appears that if you have any sort of constraint it fails with the following message:
"Msg 5074, Level 16, State 1, Line 1
The object 'MY_CLUSTERED_INDEX' is dependent on column 'my_column'.
Msg 4922, Level 16, State 9, Line 1
ALTER TABLE ALTER COLUMN my_column failed because one or more objects access this column."
So, Anyone got any advice on how to change collation on columns where you have constraints without any major pain?
Cheers!
Stu.
January 21, 2008 at 11:46 pm
Check the following link may be useful
http://drsql.spaces.live.com/blog/cns!80677FB08B3162E4!1333.entry
January 22, 2008 at 2:01 am
Also see http://www.sqlservercentral.com/Forums/Topic443054-5-1.aspx. Same tools though. 😀 (of course I'm biased)
Regards,
Andras
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply