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 |
|
kotsas
Yak Posting Veteran
65 Posts |
 Posted - 2002-08-06 : 07:58:09
|
| Dear friends,I like to migrate my sql 7.0 database to sql 2000 with backup -restore. On test restore SQL 2000 fin out that my database have SQL_LATIN1_GENERAL_CP1_CI_AS COLLATION, and my tempdb and system tables have Macedonian_ci_as collation. Please tell me what compatibility problem I will have with this?? I'm not using tempdb.Thanks |
|
|
setbasedisthetruepath
Used SQL Salesman
992 Posts |
Posted - 2002-08-06 : 09:10:49
|
quote:
I'm not using tempdb.
Wishful thinking, I'm afraid.The SQL Server optimizer does build work tables in tempdb from time to time to aid query execution, outside the scope of explicitly referencing a table in tempdb with #tablename. Based on that I would think you would encounter collation mismatches from time to time.Jonathan Boott, MCDBA{0} |
 |
|
|
kotsas
Yak Posting Veteran
65 Posts |
Posted - 2002-08-06 : 09:46:57
|
| microsoft just say that problems can be find if we use text data type.I'm not using text data type |
|
|
|
rrb
SQLTeam Poet Laureate
1479 Posts |
Posted - 2002-12-02 : 01:28:54
|
| kotsasthe kind of problems you are likely to experience:select * from table where a = b - may not return what you expectThe collation settings effectively define how the "=" (and other comparison) operators work.You should have the same collation settings throughout unless you're specifically handling different language data separately within the same db.--I hope that when I die someone will say of me "That guy sure owed me a lot of money" |
|
|
|
|
|
|
Collation problems