Posted by Razvan Socol on 12/16/05 19:31

Hello, Ryan

In SQL Server, collations can be configured at several levels:
- the default collation for the entire server (instance)
- the default collation of the database
- the collation of the column in some table

I understand that you get the "Cannot resolve collation conflict for
equal to operation" message when you try to compare (by joining, for
example) a column from a temporary table to a column from a normal
table. In this, case the problem is caused by the fact that temporary
tables are stored in the tempdb database, so (unless you explicitly
specify a collation) they get the default collation of the tempdb
database, which is the default collation of the server.

To solve this problem without changing any code, you need to change the
default collation of the server to match the default collation of your
restored database (which is also the default collation of the live
server). In order to change the default collation of the server, you
need to "rebuild the master database" or reinstall SQL Server. See:
http://msdn.microsoft.com/library/en-us/architec/8_ar_da_3zw3.asp
http://msdn.microsoft.com/library/en-us/coprompt/cp_rebuildm_6dbt.asp

Razvan

• Next in forum: Re: dynamically trasnpose rows into columns
• Prev in forum: Re: Concurrent users
• Thread view: Re: Cannot resolve collation conflict for equal to operation.

[Reply to this message]