Article ID: 834451
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 Enterprise Edition 64-bit
- Microsoft SQL Server 2000 Developer Edition
Bug #: 470576 (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.
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
It takes more time than expected to restore the transaction log files in SQL Server 2000. The transaction log restore operation may take 100 times longer or more than a typical restore operation. For example, you may experience that a 100 MB transaction log file now takes 20 minutes to be restored instead of the 12 seconds that it generally takes on the same system. This symptom is independent of any system workload.
Note You may notice this problem especially in a log shipping scenario because it will probably lead log shipping to run out of synchronization.
For a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, see the following article in the Microsoft Knowledge Base:
810185 SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a
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 How to obtain the latest SQL Server 2000 service pack
Hotfix information
Prerequisites
You must install SQL Server 2000 Service Pack 3. 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 have to 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.
SQL Server 2000, 32-bit versions
Date Time Version Size File name -------------------------------------------------------------- 02-Jan-2004 19:42 2000.80.904.0 287,304 Rinitcom.dll 02-Jan-2004 19:42 2000.80.904.0 53,832 Snapshot.exe 02-Jan-2004 19:41 2000.80.904.0 28,672 Sqlagent.dll 02-Jan-2004 19:42 2000.80.904.0 311,872 Sqlagent.exe 28-Dec-2003 01:55 2000.80.904.0 7,606,353 Sqlservr.exe
SQL Server 2000, 64-bit version
Date Time Version Size File name Platform ----------------------------------------------------------------------------- 03-Jan-2004 18:52 2000.80.904.0 56,832 Dbmslpcn.dll IA-64 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 02-Jan-2004 21:24 10,315 Hotfix1.inf 24-Apr-2003 02:51 747,927 Instdist.sql 03-May-2003 01:56 1,581 Inst_repl_hotfix.sql 03-Jan-2004 18:52 2000.80.904.0 185,856 Msgprox.dll IA-64 01-Apr-2003 02:07 1,873 Odsole.sql 03-Jan-2004 18:52 2000.80.904.0 150,528 Odsole70.dll IA-64 03-Jan-2004 18:52 2000.80.904.0 27,136 Opends60.dll IA-64 03-Jan-2004 18:51 2000.80.904.0 148,992 Osql.exe IA-64 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 03-Jan-2004 18:52 2000.80.904.0 534,016 Replprov.dll IA-64 03-Jan-2004 18:52 2000.80.904.0 769,024 Replrec.dll IA-64 06-Sep-2003 00:00 1,087,150 Replsys.sql 13-Aug-2003 16:28 986,603 Repltran.sql 03-Jan-2004 18:52 2000.80.904.0 650,240 Rinitcom.dll IA-64 03-Jan-2004 18:52 2000.80.904.0 132,608 Semnt.dll IA-64 03-Jan-2004 18:51 2000.80.904.0 89,088 Snapshot.exe IA-64 05-Aug-2003 21:06 127,884 Sp3_serv_uni.sql 02-Jan-2004 21:34 2000.80.904.0 10,240 Sqlagent.dll IA-64 03-Jan-2004 18:51 2000.80.904.0 1,055,744 Sqlagent.exe IA-64 03-Jan-2004 18:52 2000.80.904.0 812,032 Sqldata.dll IA-64 03-Jan-2004 18:52 2000.80.904.0 13,845,504 Sqldmo.dll IA-64 03-Jan-2004 18:51 39,936 Sqldumper.exe IA-64 03-Jan-2004 07:24 2000.80.904.0 19,968 Sqlevn70.rll 03-Jan-2004 18:52 2000.80.904.0 23,040 Sqlmap70.dll IA-64 03-Jan-2004 18:52 2000.80.904.0 152,064 Sqlrepss.dll IA-64 03-Jan-2004 18:52 2000.80.904.0 24,894,464 Sqlservr.exe IA-64 03-Jan-2004 18:52 2000.80.904.0 616,960 Sqlsort.dll IA-64 03-Jan-2004 18:52 2000.80.904.0 120,320 Sqlvdi.dll IA-64 06-Jan-2004 00:29 2000.80.904.0 53,760 Ssmslpcn.dll IA-64 03-Jan-2004 18:52 2000.80.904.0 254,976 Ssnetlib.dll IA-64 03-Jan-2004 18:52 2000.80.904.0 20,992 Ssnmpn70.dll IA-64 03-Jan-2004 18:52 2000.80.904.0 430,080 Svrnetcn.dll IA-64 03-Jan-2004 18:52 2000.80.904.0 185,856 Svrnetcn.exe IA-64 03-Jan-2004 18:52 2000.80.904.0 187,392 Xpweb70.dll IA-64
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 bug 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 KB834451
