SQL Server 2000 Collation Problem

Question

0.00/5 (No votes)

See more:

Hi all,

I'm using a SQL Server 2000 DB which interacts with an SQL Server 2005 DB on a remote machine via linked server.
Every thing works fine, except updating some columns in the source-tables on the remote machine:"Cannot resolve collation conflict for equal to operation" is the message I always get.

I'm working with temporary tables (#TempTbl e.g.) where I store results when I query the source tables and I want to use the same results to update the source tables "read by client"-column - but it always fails.

Ialso changed the collation locally (#TempTbl) to the remote DBs collation before comparing it but it does not help.

Can anybody tell me what I'm doing wrong or is this issue related to the #TempTbl? Has anybody an alternative solution to my problem?

Thanks in advance.

d-as_2009

Posted 21-Jan-12 1:59am

d-as_2010

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

E.F. Nijboer · Answer 1 · 2012-01-21T06:38:00

A collation defines the code page sort order for unicode data types and code page characters. The error you get tells you that the definition between the two columns doesn't match so you need to explicitly specify what collation should be used, like this:

SQL

SELECT id
  FROM TmpTable1
  INNER JOIN TmpTable2
  WHERE TmpTable1.name COLLATE DATABASE_DEFAULT = TmpTable2.name COLLATE DATABASE_DEFAULT

Good luck!

d-as_2010 · Answer 2 · 2012-01-21T09:23:00

Thanks E.F. Nijboer for your post. The solution you provide I 've already checked - with no success (... "I also changed the collation locally (#TempTbl) to the remote DBs collation" ...).

But I probably found another way to fix this problem (thanks to http://onlytalkingsense.wordpress.com):

..."The easiest way to fix this is to let SQL Server create the temp table for you via a SELECT INTO statement:

SELECT name, firstName
FROM somewhere
INTO #MyTempTable

The temp table will still be created in tempdb, but it’s fields will take the collation from their source (in this case, the fields in the <somewhere> table." ...

SQL Server 2000 Collation Problem

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0