Microsoft Windows XP and Microsoft Windows Server 2003
include several new Windows locales that are not supported by the SQL Server
2000 collation mappings. Additionally, these Windows locales are not supported
by SQL Server Desktop Engine and SQL Server Desktop Engine (Windows). The
following locales are not supported by SQL Server 2000 collation mappings:
Collapse this tableExpand this table
Language | Country/Region | LCID (hexadecimal) |
Kyrgyz (Cyrillic) | Republic of
Kyrgyzstan | 440 |
Uzbek (Latin) | Republic of Uzbekistan | 443 |
Tatar | Tatarstan | 444 |
Punjabi (Gurmukhi) | India | 446 |
Gujarati | India | 447 |
Tamil | India | 449 |
Mongolian (Cyrillic) | Mongolia | 450 |
Galician | Spain | 456 |
Konkani | India | 457 |
Uzbek (Cyrillic) | Republic of
Uzbekistan | 843 |
Armenian | Republic of Armenia | 042b |
Azeri (Latin) | Azerbaijan | 042c |
Kazakh | Kazakstan | 043f |
Telugu | India | 044a |
Kannada | India | 044b |
Marathi | India | 044e |
Sanskrit | India | 044f |
Syriac | Syria | 045a |
Azeri (Cyrillic) | Azerbaijan | 082c |
Chinese | Hong Kong | 0c04 |
Spanish | Colombia | 240a |
Set up verbose logging
When you run the Setup.exe file that is included in the Setup
program to install SQL Server Desktop Engine, you can enable verbose logging
for troubleshooting purposes by using the
L*v command-line switch. The following sample command enables verbose
logging:
D:\MSDE2000\>setup.exe /settings setup.ini D:\MSDE2000\setup.ini /L*v C:\MSDE_setup.log
Note In this command, a Setup.ini file that contains the settings for
the TARGETDIR argument, the DATADIR argument, the INSTANCENAME argument, and
the COLLATION argument is specified. If you specify the
/settings option, you set these options in the .ini file, not in the
command-line arguments. The previous command assumes that the .ini file is in
the same folder as the Setup.exe file.
For more information about the
SQL Server Desktop Engine Setup program, visit the following Microsoft Web
site: