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-09-24 : 09:45:20
|
| Tino writes "Hi all. I am a first timer in this forum.I am trying to duplicate duplicate a SQL Server 7 database on one SQL server to another one. The fist one runs Windows NT 4 and sp_helpsort shows Locale ID = 33282, le latter is a Windows 2000 server with Locale ID= 1033 (US English). My PC, a client, also shows Locale ID = 1033.I detached the DB from the Win NT 4 server, copied the data and log files onto the Win 2000 server, reattached the files on the NT 4 server, all that was fine. Now, when I try to attach the files on the Win 2000 server I get an error saying that the files cannot be attached because of the different locales, does anyone have any idea how to fix this problem?Why is is that the locale are different while Regional Settings as well as Time Zones (US Eastern) are the same?I await your assistance." |
|
|
solart
Posting Yak Master
148 Posts |
Posted - 2002-09-24 : 11:14:17
|
| localeThe Windows operating-system attribute that defines certain behaviors related to language. The locale defines the code page, or bit patterns, used to store character data, and the order in which characters are sorted. It also defines language-specific items such as the format used for dates and time and the character used to separate decimals in numbers. Each locale is identified by a unique number, called a locale identifier or LCID. SQL Server 2000 collations are similar to locales in that the collations define language-specific types of behaviors for instances of SQL Server 2000.My guess is that the SQL Server 2000 collation is incompatible with the defined Windows locale setting.Can anyone else explain the relationship between Windows and SQL Server collation? What is compatible and what is not compatible, etc.Anyone else? |
 |
|
|
|
|
|
|
|