I'm getting the following error on a procedure:
Msg 446, Sev 16: Cannot resolve collation conflict for equal to operation. [SQLSTATE 42000]
Job 'DPSU Remove Employee Subgroup' : Step 1, 'REMOVE EMPLOYEE SUBGROUP' : Began Executing 2007-08-09 08:00:00
From what I've found, this can occur when the collation of the database doesn't match the master or tempdb collation. However, they all match.
One pertinent issue, is that the Instance this DB originated from does have a different collation to the one it resides on now.
Latin1-General,Case-Insensitive,Accent-Sensitive,Kanatype-Insensitive,Width-Insensitive Unicode Data,Sort Order 52 for non unicode data
These procedures have worked for about 3 years without a problem. They were written by the Application Vendor, so even if putting in a Collate statement resolves the problem, the procedures would then become unsupported.
The only thing I can think of is to get a completely new server, install MSSQL with the exact same Collation, and restore the db onto there and test. Only thing is that this DB has gone into production, so they're not going to be keen.
Are there any alternatives, or would I have to start afresh with a new install?