Article ID: 832437 - Last Review: November 2, 2007 - Revision: 2.3

FIX: A CHECKDB statement reports corruption after SQL Server transfers sql_variant data in SQL Server 2000

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

Bug # 470559 (SQL Server 8.0)

SYMPTOMS

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 ).

Back to the top

RESOLUTION

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 (http://support.microsoft.com/kb/290211/ ) How to obtain the latest SQL Server 2000 service pack

Back to the top

Hotfix information

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.

   Date         Time   Version            Size    File name
   ---------------------------------------------------------------------------
   31-May-2003  18:45  2000.80.818.0      78,400  Console.exe      
   28-Oct-2003  04:21  2000.80.873.0     315,968  Custtask.dll     
   02-Oct-2003  20:59  2000.80.867.0      33,340  Dbmslpcn.dll     
   25-Apr-2003  02:12                    786,432  Distmdl.ldf
   25-Apr-2003  02:12                  2,359,296  Distmdl.mdf
   30-Jan-2003  01:55                        180  Drop_repl_hotfix.sql
   12-Sep-2003  03:26  2000.80.859.0   1,905,216  Dtspkg.dll       
   26-Aug-2003  20:16  2000.80.854.0     528,960  Dtspump.dll      
   23-Jun-2003  22:40  2000.80.837.0   1,557,052  Dtsui.dll        
   23-Jun-2003  22:40  2000.80.837.0     639,552  Dtswiz.dll       
   24-Apr-2003  02:51                    747,927  Instdist.sql
   03-May-2003  01:56                      1,581  Inst_repl_hotfix.sql
   08-Feb-2003  06:40  2000.80.765.0      90,692  Msgprox.dll      
   01-Apr-2003  02:07                      1,873  Odsole.sql
   05-Apr-2003  01:46  2000.80.800.0      62,024  Odsole70.dll     
   07-May-2003  20:41  2000.80.819.0      25,144  Opends60.dll     
   02-Apr-2003  21:48  2000.80.796.0      57,904  Osql.exe         
   02-Apr-2003  23:15  2000.80.797.0     279,104  Pfutil80.dll     
   04-Aug-2003  18:17                    550,780  Procsyst.sql
   12-Sep-2003  00:37                     12,305  Qfe469315.sql
   22-May-2003  22:57                     19,195  Qfe469571.sql
   06-Sep-2003  01:36                  1,090,932  Replmerg.sql
   06-Sep-2003  07:18  2000.80.858.0     221,768  Replprov.dll     
   06-Sep-2003  07:18  2000.80.858.0     307,784  Replrec.dll      
   06-Sep-2003  00:00                  1,087,150  Replsys.sql
   13-Aug-2003  16:28                    986,603  Repltran.sql
   22-Oct-2003  00:08  2000.80.871.0      57,916  Semnt.dll        
   29-Jul-2003  20:13  2000.80.819.0     492,096  Semobj.dll       
   31-May-2003  18:27  2000.80.818.0     172,032  Semobj.rll
   05-Aug-2003  21:06                    127,884  Sp3_serv_uni.sql
   01-Jun-2003  01:01  2000.80.818.0   4,215,360  Sqldmo.dll       
   07-Apr-2003  17:44                     25,172  Sqldumper.exe    
   19-Mar-2003  18:20  2000.80.789.0      28,672  Sqlevn70.rll
   27-Sep-2003  04:42  2000.80.865.0     180,792  Sqlmap70.dll     
   03-Sep-2003  02:56  2000.80.857.0     188,992  Sqlmmc.dll       
   02-Sep-2003  23:03  2000.80.857.0     479,232  Sqlmmc.rll
   22-Oct-2003  00:08  2000.80.871.0     401,984  Sqlqry.dll       
   08-Feb-2003  06:40  2000.80.765.0      57,920  Sqlrepss.dll     
   11-Nov-2003  22:34  2000.80.878.0   7,606,353  Sqlservr.exe     
   25-Jul-2003  21:44  2000.80.845.0     590,396  Sqlsort.dll      
   08-Feb-2003  06:40  2000.80.765.0      45,644  Sqlvdi.dll       
   02-Oct-2003  20:59  2000.80.867.0      33,340  Ssmslpcn.dll     
   01-Jun-2003  01:01  2000.80.818.0      82,492  Ssnetlib.dll     
   01-Jun-2003  01:01  2000.80.818.0      25,148  Ssnmpn70.dll     
   28-Oct-2003  04:21  2000.80.873.0     123,456  Stardds.dll      
   01-Jun-2003  01:01  2000.80.818.0     158,240  Svrnetcn.dll     
   31-May-2003  18:59  2000.80.818.0      76,416  Svrnetcn.exe     
   30-Apr-2003  23:52  2000.80.816.0      45,132  Ums.dll          
   02-Jul-2003  00:19  2000.80.834.0      98,816  Xpweb70.dll

Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Back to the top

STATUS

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.

Back to the top

MORE INFORMATION

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.

Back to the top