Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQLServer 2000. Collation conflict


SQLServer 2000. Collation conflict

Author
Message
Gosta Munktell
Gosta Munktell
SSC Veteran
SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)

Group: General Forum Members
Points: 222 Visits: 1406

Hi,

A logfile SQLAGENT.out is created and updated three times a minute with:

[298] SQLserver Errror: 446, Cannot resolve collation conflict for equal to operation. [SQLSTATE 42000].

I have tryed to find an explanation to this error and set the collation on the databases as recomended.

What can I do?

Thanks in advance

Gosta M


Jo Pattyn
Jo Pattyn
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1589 Visits: 9720

be aware that a field in a table can have a different collation than the default collation for a database.

1) find the query/command causing the trouble

2) check all the fields and their collation

3) check also the collation of tempdb

There is also a Collate command, but I haven't used it yet except for scripting tables.


Gosta Munktell
Gosta Munktell
SSC Veteran
SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)SSC Veteran (222 reputation)

Group: General Forum Members
Points: 222 Visits: 1406

Thank you

The thing is that the logg is created all the time. No queries etc are running.

be aware that a field in a table can have a different collation than the default collation for a database.

In this application there is no need for different collation for each field. Is there a way to set all collations to

<database default> to each field/table in a database without going throw all of them?

Tia

Gosta


wim hartmans-453506
wim hartmans-453506
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 53

think you have to go through all fields...

like jo said: single field in a table can have different collation from the table. There is no way

Of course you can do some reverse enginering: since when does this message appear in logs? which table\field was created then?

don't know a command that can set collation for all objects in one time. option might be to make a query whith a cursor that loop s through all sysobjects...nested cursor that finds all columns in a table and then execute an alter database command..

good luck


Markus2006
Markus2006
SSC Rookie
SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)SSC Rookie (32 reputation)

Group: General Forum Members
Points: 32 Visits: 60
I think that if you start Profiler, you will see the queries. Maybe Agent service is running some procedures in background. Or check whether you have any active jobs.
Such problems are caused by different collations between database and server. In SQL Management Studio you can check it by selecting Server->Properties and Database->Properties.
The problem may be caused for example by a stored procedure that uses "SELECT * into #temptable FROM ..." and later uses joins between this temporary table and a table from a database (TEMPDB and this database have different collations in this case).

Marek



Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search