"cannot resolve collation conflict for equal to operation" when running view

Get the message "cannot resolve collation conflict for equal to
operation" in a view when a have restored a database on an other
computer. In this view I compare fields from myDB and master. Have
changed so I have the same collation for all my databases om SQL
Server, but still get this problem. Anyone has a suggestion?
//di6pejo
Have you checked that the columns you are comparing actually have the same
collation. Changing the collation of the database does _not_ change the
collation of the columns that exist already in the database, it only
provides a default collation for newly created columns.
Jacco Schalkwijk
SQL Server MVP
"Peter" <ingeskrap@.tjohoo.se> wrote in message
news:3aa71bd7.0407140151.4b78d2d0@.posting.google.c om...
> Get the message "cannot resolve collation conflict for equal to
> operation" in a view when a have restored a database on an other
> computer. In this view I compare fields from myDB and master. Have
> changed so I have the same collation for all my databases om SQL
> Server, but still get this problem. Anyone has a suggestion?
> //di6pejo
|||Big thanks, seem like it worked to change one of the fields is a table.
One questions though, in the setting "SQL_LAtin1_General_CP1_CI_AS" What
does "CP1" stands for?
//Peter
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||CP1 stands for codepage 1, which isn't actually codepage 1, but codepage
1252. It is the ANSI standard codepage (loosely translated as character
set), and is used by English and most other Western European languages. For
more information look up "code page" in BOL.
Jacco Schalkwijk
SQL Server MVP
"Pejo" <ingeskrap@.tjohoo.se> wrote in message
news:OuFu3TZaEHA.2520@.TK2MSFTNGP12.phx.gbl...
> Big thanks, seem like it worked to change one of the fields is a table.
> One questions though, in the setting "SQL_LAtin1_General_CP1_CI_AS" What
> does "CP1" stands for?
> //Peter
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!

"cannot resolve collation conflict for equal to operation" when running view

Get the message "cannot resolve collation conflict for equal to
operation" in a view when a have restored a database on an other
computer. In this view I compare fields from myDB and master. Have
changed so I have the same collation for all my databases om SQL
Server, but still get this problem. Anyone has a suggestion?
//di6pejoHave you checked that the columns you are comparing actually have the same
collation. Changing the collation of the database does _not_ change the
collation of the columns that exist already in the database, it only
provides a default collation for newly created columns.
Jacco Schalkwijk
SQL Server MVP
"Peter" <ingeskrap@.tjohoo.se> wrote in message
news:3aa71bd7.0407140151.4b78d2d0@.posting.google.com...
> Get the message "cannot resolve collation conflict for equal to
> operation" in a view when a have restored a database on an other
> computer. In this view I compare fields from myDB and master. Have
> changed so I have the same collation for all my databases om SQL
> Server, but still get this problem. Anyone has a suggestion?
> //di6pejo|||Big thanks, seem like it worked to change one of the fields is a table.
One questions though, in the setting "SQL_LAtin1_General_CP1_CI_AS" What
does "CP1" stands for'
//Peter
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||CP1 stands for codepage 1, which isn't actually codepage 1, but codepage
1252. It is the ANSI standard codepage (loosely translated as character
set), and is used by English and most other Western European languages. For
more information look up "code page" in BOL.
Jacco Schalkwijk
SQL Server MVP
"Pejo" <ingeskrap@.tjohoo.se> wrote in message
news:OuFu3TZaEHA.2520@.TK2MSFTNGP12.phx.gbl...
> Big thanks, seem like it worked to change one of the fields is a table.
> One questions though, in the setting "SQL_LAtin1_General_CP1_CI_AS" What
> does "CP1" stands for'
> //Peter
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!

"cannot resolve collation conflict for equal to operation" when running view

Get the message "cannot resolve collation conflict for equal to
operation" in a view when a have restored a database on an other
computer. In this view I compare fields from myDB and master. Have
changed so I have the same collation for all my databases om SQL
Server, but still get this problem. Anyone has a suggestion?
//di6pejoHave you checked that the columns you are comparing actually have the same
collation. Changing the collation of the database does _not_ change the
collation of the columns that exist already in the database, it only
provides a default collation for newly created columns.
--
Jacco Schalkwijk
SQL Server MVP
"Peter" <ingeskrap@.tjohoo.se> wrote in message
news:3aa71bd7.0407140151.4b78d2d0@.posting.google.com...
> Get the message "cannot resolve collation conflict for equal to
> operation" in a view when a have restored a database on an other
> computer. In this view I compare fields from myDB and master. Have
> changed so I have the same collation for all my databases om SQL
> Server, but still get this problem. Anyone has a suggestion?
> //di6pejo

! PLEASE HELP !! Collation selection on install

Hi, I need to change the collation when I install SQL Express 2005 to SQL_LATIN1_GENERAL_CP1_CI_AS but the drop down on setup only allows

LATIN1_GENERAL.

How do I get the correct collation to appear?

Thanks for any help/tips

hi,

as you can see in http://msdn2.microsoft.com/en-us/library/ms144250.aspx, SQL collations are for compatibility with older settings and are not directly listed (as you want them) in the installation wizard.... you can "only" choose a Windows collation, that lists all the variations of each particular collation, or SQL collation, that you have to "customize" to fit your needs.. so, for SQL_LATIN1_GENERAL_CP1_CI_AS you have to choose Dictionary order, case-insensitive, 1252 character set (or alternate locale to fit your needs)..

regards

|||Kool....thanks a million that did the trick ;-)