VB, .NET, SQL Server, MOSS
Programming for life!
Serving the web community
with my knowledge

When you have SQL Servers with different collation settings, your databases can be different on those servers, when you don't specify the collation explicitely. To solve this, you need to alter all columns with a different collation sequence. You have to do this manually, by opening each table in the SQL Enterprise Manager, reviewing each column, and change the collation sequence. It is needless to say, this is a tedious task.
Let's describe what happens if you don't use the same collation sequence within one database. When you compare two fields with a different collation setting (SELECT * FROM MyTable WHERE Fielda = FieldB), SQL Server will give you an error: Could not resolve collation conflict for equal to operation.
You will get this error only run-time, so you can't see it until you run your stored procedures, DTS tasks, or SELECT queries. In the worst case, you will not find out, but the users will. If this is the case, then you have a big problem!
I have written a bit of T-SQL code to generate ALTER TABLE statements. Each statement fixes the collation sequence to the same name. After executing this select statement, you need to review the output, and execute it in the Query Analyzer.
Here is the T-SQL code:
Before you use this code, read the following notes:
Last modified on: 2009-02-05