Re: Cannot resolve collation conflict for equal to operation.
From: Aaron Bertrand [MVP] (aaron_at_TRASHaspfaq.com)
Date: 04/26/04
- Next message: Andrew J. Kelly: "Re: What's the deal with PAGEIOLATCH_SH?"
- Previous message: Glenn: "Cannot resolve collation conflict for equal to operation."
- In reply to: Glenn: "Cannot resolve collation conflict for equal to operation."
- Next in thread: Dan Guzman: "Re: Cannot resolve collation conflict for equal to operation."
- Messages sorted by: [ date ] [ thread ]
Date: Sun, 25 Apr 2004 22:51:00 -0400
You have one column (or database) set to one collation, and one that is set
in another. If you don't need different collations, the simplest and most
performant solution would be to make them the same collation. Otherwise,
you can make them equivalent using the COLLATE clause... see Books Online
for usage (e.g. in the WHERE clause).
-- Aaron Bertrand SQL Server MVP http://www.aspfaq.com/ "Glenn" <anonymous@discussions.microsoft.com> wrote in message news:CE360B1C-CAC8-41C0-BC66-E681AD697143@microsoft.com... > Getting this error when trying to join tables, does anyone have any > direction for me to look to solve this problem, > > I have seached the support pages at MS and found nothing that will help. > Running SQL Server service pack3 > >
- Next message: Andrew J. Kelly: "Re: What's the deal with PAGEIOLATCH_SH?"
- Previous message: Glenn: "Cannot resolve collation conflict for equal to operation."
- In reply to: Glenn: "Cannot resolve collation conflict for equal to operation."
- Next in thread: Dan Guzman: "Re: Cannot resolve collation conflict for equal to operation."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading
