This article has been archived. It is offered "as is" and will no longer be updated.
Bug # 470559 (SQL Server 8.0)
A DBCC CHECKDB statement may report consistency errors in your database when all the following conditions are true:
SQL Server loads data into a column that is a sql_variant data type.
The data originates in another column that is a sql_variant data type and at some point the data is sent on-the-wire by SQL Server. The data is sent either directly to another server that is running SQL Server or to an intermediate file.
The sql_variant column contains numeric values.
Here are some examples of statements that could cause this behavior:
An INSERT..SELECT statement that specifies a remote server in the FROM clause of the SELECT statement.
A bcp or a BULK INSERT statement from a file that was originally created by a SELECT statement from SQL Server.
A data load using Data Transformation Services.
Here are some of the error messages that you might receive:
Error message 1
Server: Msg 2537, Level 16, State 43, Line 1 Table error: Object ID 587149137, index ID 0, page (1:1325), row 0. Record check (innerLength <= innerColInfo.CbMaxLen () && innerPCol != NULL) failed. Values are 17 and 5.
Error message 2
Server: Msg 2537, Level 16, State 1, Line 1 Table error: Object ID 587149137, index ID 0, page (1:1325), row 0. Record check (Valid SqlVariant) failed. Values are 1 and 0.
Error message 3
DBCC results for 'myvar2'. There are 1 rows in 1 pages for object 'myvar2'. CHECKTABLE found 0 allocation errors and 2 consistency errors in table 'myvar2' (object ID 587149137). repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (pubs.dbo.myvar2 ).
Service pack information
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 fix has the file attributes (or later) 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.
The fix that is described in this article corrects the way that SQL Server interprets the stream of bytes as it reads the information that is being sent on-the-wire.
You apply the fix to the receiving server only. The fix does not correct the previously damaged data. To return to a well-known state, you might consider truncating the table or you can run a DBCC CHECKDB statement with the REPAIR_ALLOW_DATA_LOSS option to delete the damaged rows. Then, you can reload the table from the original data source.
For additional information about software updates, 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