This article has been archived. It is offered "as is" and will no longer be updated.
Bug #: 471459 (SHILOH_BUGS)
Microsoft distributes Microsoft SQL Server 2000 hotfixes as one downloadable file. Because the hotfixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2000 hotfix release.
Operating system, driver, or hardware problems may cause SQL Server to experience data integrity-related problems. You may receive data integrity-related error messages in the SQL Server error log. These error messages may include, but are not limited to, error messages 823, 605, 644, 625, or assertion failures that are similar to the following:
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, 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
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.
Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
This hotfix adds diagnostics to SQL Server. These diagnostics try to detect when a read operation from a disk does not experience any errors but the read operation returns data that is not valid. The validation that the diagnostics perform on the data that is returned to SQL Server is similar to audit checks by the CHECKDB command. If you enable these diagnostics, pages are audited every time that they are read from disk.
To enable these diagnostics, you must enable trace flag 806 on the server. To do this, use one of the following methods:
Add -T806 to the SQL Server startup parameters. To do this in Enterprise Manager, point to Server Properties, and then click Startup Parameters.
Use the DBCC TRACEON(806, -1) command from a query connection.
When you enable trace flag 806 and an audit failure is detected during a read operation, you will receive the following error messages in the SQL Server error log:
2004-06-25 11:29:04.11 spid51 Error: 823, Severity: 24, State: 2 2004-06-25 11:29:04.11 spid51 I/O error (audit failure) detected during read at offset 0x000000000b0000 in file 'e:\Program Files\Microsoft SQL Server\MSSQL\data\pubs.mdf'..
These error messages could indicate potential problems with the disk, the disk controller, or the disk driver software. If you receive these error messages, you must investigate these potential problems.
Note The diagnostics that are included in this hotfix do not correct any hardware or driver problems. These diagnostics are only intended to report issues that occur when you retrieve database pages from physical media.For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Microsoft SQL Server 2000 Developer Edition, Microsoft SQL Server 2000 Standard Edition, Microsoft SQL Server 2000 Enterprise Edition, Microsoft SQL Server 2000 Personal Edition, Microsoft SQL Server 2000, Workgroup Edition, Microsoft SQL Server 2000 Desktop Engine (Windows), Microsoft SQL Server 2000 Enterprise Edition 64-bit