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.
| Author |
Topic |
|
acl123
Starting Member
2 Posts |
 Posted - 2008-11-08 : 18:11:58
|
| We have recently moved our database to a different machine and also upgrade Management Studio from 2005 to 2008 (we haven't upgraded the database tho).I created a new column in a table but it is now giving me collation conflict errors when I compare the column to an older table's column:Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.The database now has its default collation set to SQL_Latin1_General_CP1_CI_AS, but when I select Properties-Options there is no option for "Latin1_General_CI_AS", so I cannot change the default back to how it should be.If I open the older table in design view and try to change the collation I get this error message popping up:Object reference not set to an instance of an objectThis looks like a bug in Management Studio 2008.Anyone know a way of fixing this problem? I don't want to have to always specify the collation on every column because there are 100s of tables and it would become a maintenance nightmare. |
|
|
acl123
Starting Member
2 Posts |
Posted - 2008-11-08 : 23:45:17
|
| I solved this problem - I didn't notice the "SQL_" at the beginning of the collation name. Silly me! |
 |
|
|
|
|
|
Default collation changed