Posted by sdwebguy on 04/10/06 20:14

I am running into the same problem.

We have a server that was running SQL 2000. Complete uninstall of 2000.
Complete fresh install of SQL 2005. Then we used the 2000 to 2005
migration wizard to copy the app databases from another 2000 server to
the new 2005 server.

When I run these statements:
select name, collation_name, compatibility_level from sys.databases
select serverproperty('Collation')

I get these results:

master Latin1_General_CI_AI 90
tempdb Latin1_General_CI_AI 90
model Latin1_General_CI_AI 90
msdb Latin1_General_CI_AI 90
appdb1 SQL_Latin1_General_CP1_CI_AS 90
appdb2 SQL_Latin1_General_CP1_CI_AS 90

Latin1_General_CI_AI

We get errors in our app because we use tempDB for some ## temp tables.


On our development server, the system databases are all
SQL_Latin1_General_CP1_CI_AS and the serverproperty('Collation') also
returns SQL_Latin1_General_CP1_CI_AS. So Im not sure what the best way
to proceed is. Should I just create new databases on production to
match the Latin1 collation? If we bring those databases down to
development, will be have problems on development with unmatched
collation errors?

Tim

• Next in forum: Re: Re-display result set without re-running query in Query Analyzer?
• Prev in forum: Configuring Peer-to_Peer Merge Replication
• Thread view: Re: SQL Server 2005: Collation Conflict Error when selecting Database Properties

[Reply to this message]