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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2002-08-01 : 09:00:35
|
| Yves writes "Hi,I have a problem when I restore a SQL Server 7 to SQL 2000 database . This is our server configuration :- SQL Server 7, the code page is CP 850, Sorted order 44 noaccents_850 Dictionary order, case-insensitive, accent-insensitive ;- SQL Server 2000, the code page is SQL_Latin1_General_CP850_CI_AI (Latin1-General, case-insensitive, accent-insensitive, kanatype-insensitive, width-insensitive for Unicode Data, SQL Server Sort Order 44 on Code Page 850 for non-Unicode Data);When I restore a database in SQL Server 2000 from a SQL Server 7 backup file , the collation name of database and columns are set to "Compatibility_44_40c_3" ??? I can change this collation name only for the database with an ALTER DATABASE but not for the columns of all existing tables.I would like to know why the database's collation is set to "Compatibility_44_40c_3" and not to "SQL_Latin1_General_CP850_CI_AI" ?àty for your help" |
|
|
Argyle
Yak Posting Veteran
53 Posts |
Posted - 2002-08-04 : 10:55:51
|
| There must be something that is different, otherwise SQL would have chosen the collation you mention. For example what are the unicode settings on the SQL 7 database, are they different from the non-unicode settings? In SQL 7 these settings didn't have to match.What you can do is to create a new database with correct collation and BCP out the data from your restored backup and in to the new one. Otherwise you have to alter each column as you say.There is a KB that might help you locate the diffrence:INF: Description of SQL Server Compatibility Collationshttp://support.microsoft.com/default.aspx?scid=kb;EN-US;Q270042 |
 |
|
|
|
|
|
|
|