September 16, 2007 at 11:10 am
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
September 17, 2007 at 4:53 am
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.
September 18, 2007 at 6:41 am
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
September 19, 2007 at 4:47 pm
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
March 12, 2008 at 5:09 am
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
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply