FIX: You may receive an error message when you set the database collation to Thai_CI_AS and you try to run a Transact-SQL update query in SQL Server 2000 (910895)
The information in this article applies to:
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Enterprise Edition
- Microsoft SQL Server 2000 Personal Edition
- Microsoft SQL Server 2000 Standard Edition
- Microsoft SQL Server 2000 Developer Edition 64 bit
- Microsoft SQL Server 2000 Enterprise Edition 64-bit
Bug #: 474725 (SQL Server 8.0)
Microsoft distributes Microsoft SQL Server 2000 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 fix release. This article describes the following about this hotfix
release:
- The issues that are fixed by this hotfix package
- The prerequisites for installing the hotfix
package
- Information about whether you must restart the computer after you install the
hotfix package
- Information about whether the hotfix package is replaced by any other hotfix
package
- Information about whether you must make any registry changes
- The files that are contained in the hotfix
package
SYMPTOMSWhen you try to run a Transact-SQL update query in Microsoft
SQL Server 2000, you may receive the following error message: Server: Message 644, Severity 21, State 5, Line 1 Could not
find the index entry for RID '163ca00000010000' in index page (1:358), index ID
2, database 'DatabaseName'. Connection
Broken. You experience this problem when all the following
conditions are true:
- You set the database collation to Thai_CI_AS.
- You create a clustered index on a column, and the column is the int data
type.
- You create a non-clustered index on a column, and the column is the varchar data type.
Note You do not receive a corruption message when you run the DBCC CHECKDB command. For a list of all publicly released SQL Server
2000 Post-Service Pack hotfixes, see the following article in the Microsoft
Knowledge Base: 894905 Cumulative list of the hotfixes
that are available for SQL Server 2000 SP4
CAUSEThis problem occurs because the comparison functions do not
correctly compare values when you use the Thai_CI_AS collation.RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next SQL Server 2000 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesYou must have Microsoft SQL Server 2000 Service Pack 4 (SP4)
installed to apply this hotfix.
For more information about how to obtain SQL Server 2000 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:
290211
How to obtain the latest SQL Server 2000 service pack
Restart informationYou do not have to restart the computer after you apply this
hotfix. Registry informationYou do not have to change the registry after you apply this hotfix. Hotfix file informationThis hotfix contains only those files that are required to correct
the issues that this article lists. This hotfix may not contain of all the
files that you must have to fully update a product to the latest
build.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. SQL Server 2000 32-bit versions|
Dtsui.dll | 2000.80.2171.0 | 1,593,344 | 04-Nov-2005 | 07:10 | x86 | Impprov.dll | 2000.80.2171.0 | 102,400 | 04-Nov-2005 | 07:10 | x86 | Mssdi98.dll | 8.11.50523.0 | 239,104 | 06-Jun-2005 | 22:46 | x86 | Ntwdblib.dll | 2000.80.2171.0 | 290,816 | 04-Nov-2005 | 07:10 | x86 | Odsole70.dll | 2000.80.2171.0 | 69,632 | 04-Nov-2005 | 07:10 | x86 | Pfclnt80.dll | 2000.80.2171.0 | 430,080 | 04-Nov-2005 | 07:10 | x86 | Replprov.dll | 2000.80.2171.0 | 237,568 | 04-Nov-2005 | 07:10 | x86 | Semexec.dll | 2000.80.2171.0 | 856,064 | 04-Nov-2005 | 07:10 | x86 | Sqlagent.exe | 2000.80.2171.0 | 323,584 | 04-Nov-2005 | 05:27 | x86 | Sqldiag.exe | 2000.80.2171.0 | 118,784 | 04-Nov-2005 | 06:09 | x86 | Sqldmo.dll | 2000.80.2171.0 | 4,362,240 | 04-Nov-2005 | 07:10 | x86 | Sqlfth75.dll | 2000.80.2171.0 | 102,400 | 04-Nov-2005 | 05:33 | x86 | Sqlservr.exe | 2000.80.2171.0 | 9,158,656 | 04-Nov-2005 | 07:10 | x86 | Sqlsort.dll | 2000.80.2171.0 | 589,824 | 04-Nov-2005 | 07:10 | x86 | Stardds.dll | 2000.80.2171.0 | 176,128 | 04-Nov-2005 | 07:10 | x86 | Svrnetcn.dll | 2000.80.2171.0 | 110,592 | 04-Nov-2005 | 07:10 | x86 | Ums.dll | 2000.80.2171.0 | 35,328 | 04-Nov-2005 | 07:10 | x86 | Sqlevn70.rll | 2000.80.2171.0 | 45,056 | 04-Nov-2005 | 07:10 | Not Applicable |
SQL Server 2000 Itanium architecture version|
Impprov.dll | 2000.80.2171.0 | 244,736 | 04-Nov-2005 | 07:13 | IA-64 | Mssdi98.dll | 8.11.50523.0 | 758,784 | 06-Jun-2005 | 22:46 | IA-64 | Odsole70.dll | 2000.80.2171.0 | 150,528 | 04-Nov-2005 | 07:12 | IA-64 | Pfclnt80.dll | 2000.80.2171.0 | 1,187,840 | 04-Nov-2005 | 07:30 | IA-64 | Replprov.dll | 2000.80.2171.0 | 538,624 | 04-Nov-2005 | 07:19 | IA-64 | Sqlagent.exe | 2000.80.2171.0 | 1,061,376 | 04-Nov-2005 | 07:37 | IA-64 | Sqldiag.exe | 2000.80.2171.0 | 334,336 | 04-Nov-2005 | 07:32 | IA-64 | Sqldmo.dll | 2000.80.2171.0 | 13,860,352 | 04-Nov-2005 | 07:41 | IA-64 | Sqlfth75.dll | 2000.80.2171.0 | 246,784 | 04-Nov-2005 | 07:15 | IA-64 | Sqlservr.exe | 2000.80.2171.0 | 24,921,600 | 04-Nov-2005 | 13:24 | IA-64 | Sqlsort.dll | 2000.80.2171.0 | 617,472 | 04-Nov-2005 | 05:23 | IA-64 | Svrnetcn.dll | 2000.80.2171.0 | 427,520 | 04-Nov-2005 | 07:27 | IA-64 | Sqlevn70.rll | 2000.80.2171.0 | 35,328 | 04-Nov-2005 | 13:24 | Not Applicable |
WORKAROUNDTo work around this problem, change the varchar data
type column to the nvarchar data type.STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
---|
Keywords: | kbfix kbBug kbHotfixServer kbQFE kbpubtypekc KB910895 kbAudITPRO kbAudDeveloper |
---|
|