May 3, 2010 at 11:24 pm
Can we execute a join on two tables with different collation settings? Why or why not?
"Cannot resolve collation conflict for equal to operation." -Does this error always occur or are there any specific cases when this error occurs...? Is there any workaround or this problem?
Would be great if someone would clarify my doubts...
May 4, 2010 at 1:18 am
Below link contains explanation as well as workaround for your problem
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
May 4, 2010 at 5:01 am
Thanks for replying..
May 4, 2010 at 5:30 am
deepthi818 (5/4/2010)
Thanks for replying..
still you need any help , you are welcome:-)
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
May 4, 2010 at 6:36 am
deepthi818 (5/3/2010)
Can we execute a join on two tables with different collation settings? Why or why not?"Cannot resolve collation conflict for equal to operation." -Does this error always occur or are there any specific cases when this error occurs...? Is there any workaround or this problem?
Would be great if someone would clarify my doubts...
It will happen on any character based fields. So (n)(var)char etc as it needs to compare the codepages. Numeric you will be fine with.
Is this a production database or just in test? If the collation issue has been caused by error it may be wise to just setup the database again.
I see the issue all the time when the regional settings of the machine are left as US and SQL installed with default collation. Then on another server the regional settings will be correctly set to UK and this uses a different codepage. Pain in the arse to say the least!
May 4, 2010 at 9:22 am
I just encountered the situation while i was testing... not very critical.. Thanks for helping guys!
May 4, 2010 at 1:53 pm
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply