Cannot Resolve collation conflict [SQLSTATE 42000]

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.

Original DB=
Latin1-General,Case-Insensitive,Accent-Sensitive,Kanatype-Insensitive,Width-Insensitive Unicode Data,Sort Order 52 for non unicode data

New DB=

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?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Rebuild the master database with the original collation.

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Beeb_HogweedAuthor Commented:
In this case, that means installing SQL Server fresh, as there are other DB's on this instance. It was a case of them being cheapskates not getting a separate server for this DB. I'll install afresh with the same collation and try again.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.