Collation change on upgrades

[Ambientguitar]

When database upgraded from SQL 7.0 to SQL 2000 some of our code falls over because collation on some fields seems to have changed from database default to Latin1_General for some reason. This only appears to be a problem when queries doing cross joins? Also appears to only effect new fields that are created.I wonder if any of you might have a suggestion , perhaps a stored proc to set collation on all fields to be database default. Thanks in advance and congrats to SQLDennis on his tipmaster Status!

 

[SQLDenis]

Thanks,

You can use the COLLATE clause on an ALTER DATABASE to change the default collation of the database:

ALTER DATABASE MyDatabase COLLATE French_CI_AS

Lookup "collations, changing" in BOL for more details


Denis The SQL Menace
SQL blog:

http://sqlservercode.blogspot.com/

Personal Blog:

http://otherthingsnow.blogspot.com/