Article ID: 825197
Article Last Modified on 11/2/2007
APPLIES TO
- 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 Enterprise Edition
- Microsoft SQL Server 2000 Workgroup Edition
- Microsoft SQL Server 2000 Desktop Engine (Windows)
- Microsoft SQL Server 2000 Developer Edition
- Microsoft SQL Server 2000 Enterprise Edition 64-bit
Bug #: 469496 (SQL Server 8.0)
Article contents
SUMMARY
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
- Whether you must restart your computer after you install the hotfix package
- Whether the hotfix package is replaced by any other hotfix package
- Whether you must make any registry changes
- The files that are contained in the hotfix package
SYMPTOMS
When you perform a bulk insert operation in Microsoft SQL Server 2000, the transaction log file becomes corrupted and error 3624 is written to the SQL Server error log. Subsequently, the user database is marked suspect. For example, you run the following bulk insert operation:
DELETE FROM <tableName> BULK INSERT TableName FROM 'FileName' WITH (DATAFILETYPE = 'native', TABLOCK)
When you do this, you may receive an error message that is similar to the following:
This problem occurs when one or more of the following conditions are true:
- A non-clustered index on the table exists.
- A TABLOCK query hint is used.
- The table was not truncated before you performed the bulk insert operation.
- The DBCC DBREINDEX statement was not used to rebuild indexes before you performed the bulk insert operation.
For a list of previous hotfixes, see the "Microsoft SQL Server 2000 post-Service Pack 3 or Microsoft SQL Server 2000 post-Service Pack 3a hotfixes" section in the following Microsoft Knowledge Base article:
290211 How to obtain the latest SQL Server 2000 service pack
CAUSE
This problem occurs because an access violation occurs that was caused by an assertion in the RecBase::ResizeVar function. The access violation causes a fatal exception. The fatal exception causes the exception handler to put a user database in suspect status.
back to the top
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional 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
Hotfix information
Prerequisites
You must install SQL Server 2000 Service Pack 3 (SP3) to apply this hotfix. For additional information about how to obtain SQL Server 2000 Service Pack 3, 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 information
You do not restart your computer after you apply this hotfix.
back to the top
Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain 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.
Date Time Version Size File name ------------------------------------------------------------------ 31-May-2003 19:45 2000.80.818.0 78,400 Console.exe 25-Jun-2003 02:01 2000.80.818.0 33,340 Dbmslpcn.dll 25-Apr-2003 03:12 786,432 Distmdl.ldf 25-Apr-2003 03:12 2,359,296 Distmdl.mdf 30-Jan-2003 02:55 180 Drop_repl_hotfix.sql 23-Jun-2003 23:40 2000.80.837.0 1,557,052 Dtsui.dll 23-Jun-2003 23:40 2000.80.837.0 639,552 Dtswiz.dll 24-Apr-2003 03:51 747,927 Instdist.sql 03-May-2003 02:56 1,581 Inst_repl_hotfix.sql 08-Feb-2003 07:40 2000.80.765.0 90,692 Msgprox.dll 01-Apr-2003 03:07 1,873 Odsole.sql 05-Apr-2003 02:46 2000.80.800.0 62,024 Odsole70.dll 07-May-2003 21:41 2000.80.819.0 25,144 Opends60.dll 02-Apr-2003 22:48 2000.80.796.0 57,904 Osql.exe 03-Apr-2003 00:15 2000.80.797.0 279,104 Pfutil80.dll 22-May-2003 23:57 19,195 Qfe469571.sql 11-Jul-2003 18:04 1,084,147 Replmerg.sql 04-Apr-2003 22:53 2000.80.798.0 221,768 Replprov.dll 08-Feb-2003 07:40 2000.80.765.0 307,784 Replrec.dll 11-Jul-2003 17:56 1,085,925 Replsys.sql 01-Jun-2003 02:01 2000.80.818.0 492,096 Semobj.dll 31-May-2003 19:27 2000.80.818.0 172,032 Semobj.rll 29-May-2003 01:29 115,944 Sp3_serv_uni.sql 01-Jun-2003 02:01 2000.80.818.0 4,215,360 Sqldmo.dll 07-Apr-2003 18:44 25,172 Sqldumper.exe 19-Mar-2003 19:20 2000.80.789.0 28,672 Sqlevn70.rll 02-Jul-2003 01:18 2000.80.834.0 180,736 Sqlmap70.dll 08-Feb-2003 07:40 2000.80.765.0 57,920 Sqlrepss.dll 10-Jul-2003 23:00 2000.80.840.0 7,553,105 Sqlservr.exe 08-Feb-2003 07:40 2000.80.765.0 45,644 Sqlvdi.dll 25-Jun-2003 02:01 2000.80.818.0 33,340 Ssmslpcn.dll 01-Jun-2003 02:01 2000.80.818.0 82,492 Ssnetlib.dll 01-Jun-2003 02:01 2000.80.818.0 25,148 Ssnmpn70.dll 01-Jun-2003 02:01 2000.80.818.0 158,240 Svrnetcn.dll 31-May-2003 19:59 2000.80.818.0 76,416 Svrnetcn.exe 01-May-2003 00:52 2000.80.816.0 45,132 Ums.dll 02-Jul-2003 01:19 2000.80.834.0 98,816 Xpweb70.dll
Note Because of file dependencies, the most recent hotfix 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
For additional information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499 New naming schema for Microsoft SQL Server software update packages
For additional information about the terminology that Microsoft uses when it corrects software after it is released, 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
Keywords: kbbug kbfix kbqfe kbsqlserv2000presp4fix kbhotfixserver KB825197
