Comments on: SQL SERVER – Cannot resolve collation conflict for equal to operation

By: pardhu

pardhu — Thu, 02 Feb 2012 09:00:02 +0000

Thanks u so much man :)

By: Oscar

Oscar — Tue, 31 Jan 2012 10:53:37 +0000

Thanks very much.

By: SQL SERVER – Collation and Collation Sensitivity – Quiz – Puzzle – 6 of 31 « SQL Server Journey with SQL Authority

Sun, 08 Jan 2012 01:30:47 +0000

[...] and Answers ISBN: 1466405643 Page#46-47 Find Collation of Database and Table Column Using T-SQL SQL SERVER – Cannot resolve collation conflict for equal to operation Find Database Collation Using T-SQL and SSMS Change Collation of Database Column – T-SQL Script [...]

By: bigdave

bigdave — Wed, 21 Dec 2011 14:38:00 +0000

Enormous!

By: osssman

osssman — Tue, 20 Dec 2011 21:35:56 +0000

tank so much man:)

By: Bryon Jordan

Bryon Jordan — Tue, 13 Dec 2011 21:15:08 +0000

Thanks so much!

By: Chat odasi

Chat odasi — Fri, 21 Oct 2011 10:48:58 +0000

hi Ilike it very much, I hope you will soon update your work!thanks for sharing

By: Nowafl M

Nowafl M — Sun, 16 Oct 2011 10:28:37 +0000

thank you very much

By: Danny

Danny — Thu, 13 Oct 2011 12:12:25 +0000

I just ran in to this collation issue during a data transfer. My Google search had this “old” article as the top result.

Great article, got me out of a jam. Thank you very much!

By: Raghav

Raghav — Tue, 04 Oct 2011 19:42:45 +0000

Didn’t get that?

By: Velmurugan

Velmurugan — Mon, 26 Sep 2011 11:49:22 +0000

thanks a lot…. it works…….

By: Penny

Penny — Fri, 09 Sep 2011 13:56:12 +0000

Sorry, Im confused….

I have taken a working SP from 2005 into 2008. Made no changes.

I have the problem between a tempory table and a function call in the ON clause of a JOIN.
Now the function was created in the database, and so was the tempory table, so although your solution works, I dont understand where the problem has come from.
Please can you explain how two things created in the same database can get this problem? Thanks

By: Savitha

Savitha — Thu, 18 Aug 2011 06:02:35 +0000

Even I am facing a error like this: Cannot resolve collation conflict for column 1 in SELECT statement. My querry is SET @allItems = 'SELECT CAST(iu.item_id AS varchar(max))+''/''+iu.description+''/I''+''/''+CAST(it.sequence AS varchar(max))+''/''+it.item_feature_parents as itemVal FROM ifl_item_u_Syn as iu INNER JOIN #item_ids as it ON it.item_id= iu.item_id

By: Pargat Singh Randhawa

Pargat Singh Randhawa — Sat, 13 Aug 2011 10:38:26 +0000

Wow!! Great, this really helps me a lot…

By: morìs

morìs — Wed, 03 Aug 2011 13:04:59 +0000

It works.
Thank you very much.

By: madhivanan

madhivanan — Mon, 18 Jul 2011 13:59:58 +0000

What was the error you got?

By: Forrest Pugh

Forrest Pugh — Thu, 14 Jul 2011 19:34:40 +0000

I would like to add that while this may work on a single server with heterogeneously collated databases, it *may not* work for all collation regimes, or across servers with different collation regimes selected as the default type.

In this case it is possible to generate a maintenance script that combs through the various DBs and Tables on a server and alters the collation type of the text type data contained therein.

In this scenario it can take some time to correct the issue either by updating the existing tables (expensive transaction), or by creating a backup version of the existing tables, and scripting them to be recreated with the correct collation, then reinserting the table content into the new correct table (cheaper transactions individually, but may add up to be more costly than an update).

The better solution would be to change the default collation on the odd server, which requires some down time as well.

Plan accordingly. Our scenario involves a single server collated one way with all the others collated (uniformly) in a different regime. Unfortunately this server is a primary reference and we cannot afford the downtime to correct it… we run the maintenance procedure over night to correct any new table content created that day, which is fairly effective for us.

By: Shyam

Shyam — Thu, 14 Jul 2011 17:36:27 +0000

I had a query with a union of tables both of which are from the same collation. Worked fine in 2005. Now that I have migrated to 2008, the same query is failing. Any ideas?

By: Pradeep

Pradeep — Wed, 13 Jul 2011 09:43:29 +0000

thankuuuuuuuuuuuuuuuuuuuuuu………….. its nice

By: simon

simon — Thu, 02 Jun 2011 10:02:10 +0000

thank you for using simple examples. two answers in two days!

By: Feodor

Feodor — Thu, 26 May 2011 19:51:38 +0000

And here is a good example why COLLATE database_default is NOT a good solution to the collation conflict problem: http://sqlconcept.com/2011/05/26/beware-collation-database_default/

By: Deon

Deon — Thu, 26 May 2011 12:04:13 +0000

Thank you, works nicely

By: Feodor

Feodor — Wed, 25 May 2011 14:42:46 +0000

Pinal,

it is true that this would be one way to solve the failing query, but the questions is: why are the columns with different collations? Is this a design feature, or is it a mistake?
And if we change the collation of the columns ‘on the fly’ in our query, then are we going to get the correct resultset?

Think about it – the collation is a set of rules by which the data is treated (recognized, sorted, distinguished) and if we force the query to make the collations of the join collumns equal, then will this affect the resultset?

Check this article, and let me know that you think: http://sqlconcept.com/2011/05/25/collation-concept-sql-server-database-column/

Feodor

By: Guido Maes

Guido Maes — Mon, 09 May 2011 09:40:45 +0000

I love you Pinal Dave!

By: Ashitha

Ashitha — Sat, 07 May 2011 08:56:54 +0000

Thanks