var sidebar_align = 'right';
var content_container_margin = parseInt('290px');
var sidebar_width = parseInt('270px');
Unanswered: Cannot resolve collation conflict for equal to operation.
Anyone bang into that?
RESTORED a 7.0 Datbase CP 52 to a 2k box
Built a "Privacy" db from scratch on 2k box
Looked at some table scripts and got
Ran this and got the error...any help?
OHM - sql 7
Privacy - sql 2k
Server: Msg 446, Level 16, State 9, Line 1
select * from privacy..privacy_column p inner join ohm.information_schema.tables t ON p.table_name = t.table_name
Cannot resolve collation conflict for equal to operation.
You need to use the collate keyword in the query. Going to be a pain in the neck, too. You will end up with
Because of this, I am debating whether to ban any collate statements on table creation scripts here. Just use the default. Please!
from privacy..privacy_column p inner join
ohm.information_schema.tables t ON p.table_name = t.table_name collate SQL_Latin1_General_CP1_CI_AS
Thanks, I think I got that....and the collation join and all
what a mess
But what bugs me is the 7.0 restore...seems to be CP 52 and the columns are collation
And the Northwind and the newly built scrambling DB are
So unless I forget, you can't restore a db to a server instance with a different CP...but it seems like 7's collation doesn't translate in to the standard 2k collation....
Is this correct?
Correct. The SQL collations and the Windoze collations are considered distinct even if they have the same inflection options (case and accent sensitivity).
Damn....means I have to be platform specific...
What was that movie? 1993
"I hate being right all the time" *
* disclaimer: You're kidding, right?
No, the distinction between SQL collations and Windoze collations are the same everywhere. SQL_Latin_General_BIN and Latin_General_BIN are
ALWAYS different collations.
Both of those collations came from a DDL script out of EM. You're losing me now.
One was from a restored 7.0 database on a 2k box:
And the others are from a sql server 2k built db
Are you saying the RESTORED 7.0 DB inhereted the windoze collation? Not the servers default collation?
I can not be sure, since it has been a while since I have played with SQL7, but I think someone who installed the SQL 2K box, may have played with the default settings a little. The default for an install of sql2K is SQL_latin_general_CP1_CI_AS. I forget what the default was for SQL 7, but I expect it was the same.
EDIT: Oh, and a database retains its collation, when restored. At least, when you go from SQL 2K to SQL 2K. What was the collation of the database on the SQL 7 server?
That's exactly what I think happened, and yes Brett, those collations are different.
Originally Posted by
Dev CP 53...so Ican't restore Prod CP 52 to dev..iditots...
ok so I get by CP...and restore to 2k....
Now I have a sql 2k box set up in Ireland with a standard CP, but a non standard collation?
This seems to be the out of the box collation
right? At least that's what I have...
To many cooks spoil the environment
I think you need to have somebody go to Ireland and help straighten things up! I'll go, I'll go!!!
Brett: Here is a thread that could help. Or at least commiserate.