Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rajnidas
Yak Posting Veteran
97 Posts |
 Posted - 2013-12-19 : 04:40:31
|
| hi every one, i was not able to solve pls i need help. while using store procedure in report getting error as mentioned below !Cannot resolve the collation conflict between "Latin1_General_CI_AI" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.ThanksRajnidas |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2013-12-19 : 04:46:00
|
use COLLATE clause to override the default collation settingsin all places where you compare between two varchar columns between two tables just useColumn1 COLLATE database_default = Column2 COLLATE database_default ie WHERE condition,ON condition of joins etc------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/https://www.facebook.com/VmBlogs |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2013-12-19 : 05:36:57
|
| Personally I would use either Latin1_General_CI_AI or SQL_Latin1_General_CP1_CI_AS (rather than database_default as there is a chance that that might match in some way that is undesirable)I think ??? that it is only necessary to specify the COLLATE statement on one side of the test? I have only ever done it on one side, and the "Cannot resolve the collation conflict" message has gone away, but maybe I am deluding myself?! |
|
|
|
|
|
|
error in procedure