FIX: Performance decreases over time when you back up files in SQL Server 2000 (824430)


The information in this article 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 Evaluation Edition
  • Microsoft SQL Server 2000 Workgroup Edition
  • Microsoft SQL Server 2000 Desktop Engine (MSDE)
  • Microsoft SQL Server 2000 Developer Edition 64 bit
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit

SUMMARY

Microsoft distributes 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.
back to the top

Introduction

Issues that are fixed by this hotfix package

The following issue is fixed in this Microsoft SQL Server 2000 hotfix package:
  • If the SQL Server virtual address space is highly fragmented, one of the user mode schedulers can become monopolized while you run a backup command to back up the transaction log or the database files. This behavior could cause a temporary reduction in overall transactional throughput on the server. Symptoms may include other logins or queries timing out while the backup operation runs.

    Additionally, while the backup operation runs, you may receive an error message in the SQL Server error log that is similar to the following:
    2004-11-02 10:48:46.03 server Error: 17883, Severity: 1, State: 0
    2004-11-02 10:48:46.03 server The Scheduler 1 appears to be hung. SPID 169, ECID 0, UMS Context 0x000006FBCA36F9A0.
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 most recent SQL Server 2000 Service Pack

back to the top

MORE INFORMATION

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

back to the top

Hotfix information

Prerequisites

This hotfix requires Microsoft SQL Server 2000 Service Pack 3 (SP3). For information about how to obtain SQL Server 2000 SP3, see the following article in the Microsoft Knowledge Base:

290211 How to obtain the most recent SQL Server 2000 service pack

back to the top

Restart information

You do not have to restart your computer after you apply this hotfix.

back to the top

Registry information

You do not have to create or modify any registry keys to enable 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 of 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  18:45  2000.80.818.0     78,400  Console.exe      
  25-Jun-2003  01:01  2000.80.818.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
  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     
  22-May-2003  22:57                    19,195  Qfe469571.sql
  11-Jul-2003  17:04                 1,084,147  Replmerg.sql
  04-Apr-2003  21:53  2000.80.798.0    221,768  Replprov.dll     
  08-Feb-2003  06:40  2000.80.765.0    307,784  Replrec.dll      
  11-Jul-2003  16:56                 1,085,925  Replsys.sql
  01-Jun-2003  01:01  2000.80.818.0    492,096  Semobj.dll       
  31-May-2003  18:27  2000.80.818.0    172,032  Semobj.rll
  29-May-2003  00:29                   115,944  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
  02-Jul-2003  00:18  2000.80.834.0    180,736  Sqlmap70.dll     
  08-Feb-2003  06:40  2000.80.765.0     57,920  Sqlrepss.dll     
  10-Jul-2003  22:00  2000.80.840.0  7,553,105  Sqlservr.exe     
  08-Feb-2003  06:40  2000.80.765.0     45,644  Sqlvdi.dll       
  25-Jun-2003  01:01  2000.80.818.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     
  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

REFERENCES

For additional information about the 17883 error message, click the following article number to view the article in the Microsoft Knowledge Base:

319892 New concurrency and scheduling diagnostics added to SQL Server

For additional information about the naming schema for Microsoft 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 correcting 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

back to the top
Modification Type:MinorLast Reviewed:10/25/2005
Keywords:kbHotfixServer kbQFE kbQFE kbSQLServ2000preSP4fix kbfix kbbug KB824430 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.