Monday, February 06, 2006

Collating Wasted Hours with SQL Server

Wasting time with SQL Server Collation settings. Bah.

The old system was running SQL_Latin1_General_CP1_CI_AS, the new system Latin1_General_CI_AS - this is enough to throw the above error, and a developer was seeing this when running stored procedures. Everywhere seemed to be at the same collation level, but the subtlety was that master, model and tempdb were at different collations to the user databases, and of course temporary tables reside in tempdb which was at the different collation setting from the user database...

So basically, with SQL Server 2000, your database server instance is tied very tightly indeed to your databases. Ick.


Post a Comment

<< Home