collation on system tables

how come this gives error?

Msg 468, Level 16, State 9, Line 2
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "SQL_Latin1_General_CP850_BIN" in the EXCEPT operation.

are system tables subject to collation too?


select name from VKDVUL.sys.all_objects where type = 'fn'
except
select name from VKDVUL1.sys.all_objects where type = 'fn'
LVL 5
25112Asked:
Who is Participating?
 
David ToddConnect With a Mentor Senior DBACommented:
Hi,

Welcome to the world of similar collations that need to be explicitly cast.

I've found that unless there are very good (ie vendor documented) reasons, the collation on the database should be the same as the collation on the server. As tempdb collation follows that from Model, you can have issues comparing the results from temp tables vs your databases tables if the collations are different.

Also if you install a case insensitive collation for SQL 2000, the SQL authenticated passwords are case insensitive.

Regards
  David
0
 
Anthony PerkinsConnect With a Mentor Commented:
are system tables subject to collation too?
Absolutely.  They acquire the same COLLATION as the database.

Incidentally, sys.all_objects is not a table.  It is a system VIEW.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.