FIX: A fetch on a dynamic cursor can cause unexpected results in SQL Server 2000 Service Pack 3 (887974)


The information in this article applies to:

  • Microsoft SQL Server 2000 Developer Edition SP3
  • Microsoft SQL Server 2000 Standard Edition SP3
  • Microsoft SQL Server 2000 Enterprise Edition SP3
  • Microsoft SQL Server 2000 Personal Edition SP3
  • Microsoft SQL Server 2000 Enterprise Evaluation Edition SP3
  • Microsoft SQL Server 2000 Workgroup Edition
  • Microsoft SQL Server 2000 Desktop Engine (MSDE) SP3
  • Microsoft SQL Server 2000 Developer Edition 64 bit
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit
Bug #: 470791 (SQL Server 8.0)
SQL Server 8.0:470791
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 problem is fixed in this Microsoft SQL Server 2000 hotfix package:
  • In SQL Server 2000 Service Pack 3, when you perform a fetch operation on a dynamic cursor, you may receive unexpected results. This behavior may occur when a nested loop join is used as part of the execution plan.
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

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 How to obtain the latest SQL Server 2000 service pack

Hotfix information

Prerequisites

This hotfix requires Microsoft SQL Server 2000 Service Pack 3 (SP3). 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

Additionally, this hotfix requires that you also have SQL Server 2000 hotfix build 2000.80.977 installed. For additional information about SQL Server 2000 Post SP3a hotfix build 2000.80.977, click the following article number to view the article in the Microsoft Knowledge Base:

888007 You receive a "The product does not have a prerequisite update installed" error message when you try to install a SQL Server 2000 post-Service Pack 3 hotfix

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

None

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. x86 version
   Date         Time   Version        Size       File name
   ----------------------------------------------------------
   08-Oct-2004  01:13  2000.80.980.0    664,128  Autoplt.dll      
   08-Oct-2004  01:13  2000.80.980.0    332,352  Ctasksui.dll     
   08-Oct-2004  01:13  2000.80.980.0    315,968  Custtask.dll     
   08-Oct-2004  01:13  2000.80.980.0  1,905,216  Dtspkg.dll       
   08-Oct-2004  01:13  2000.80.980.0    528,960  Dtspump.dll      
   08-Oct-2004  01:13  2000.80.980.0  1,557,052  Dtsui.dll        
   08-Oct-2004  01:13  2000.80.980.0    639,552  Dtswiz.dll       
   08-Oct-2004  01:13  2000.80.980.0    279,104  Pfutil80.dll     
   08-Oct-2004  01:13  2000.80.980.0     78,416  Sdiclnt.dll      
   08-Oct-2004  01:13  2000.80.980.0     66,112  Semmap.dll       
   08-Oct-2004  01:13  2000.80.980.0     57,916  Semnt.dll        
   08-Oct-2004  01:13  2000.80.980.0    492,096  Semobj.dll       
   30-Sep-2004  02:20  2000.80.980.0    172,032  Semobj.rll
   08-Oct-2004  01:13  2000.80.980.0  4,215,360  Sqldmo.dll       
   08-Oct-2004  01:13  2000.80.980.0    188,992  Sqlmmc.dll       
   30-Sep-2004  02:34  2000.80.980.0    479,232  Sqlmmc.rll
   08-Oct-2004  01:13  2000.80.980.0    401,984  Sqlqry.dll       
   08-Oct-2004  01:13  2000.80.980.0    123,456  Stardds.dll      
   08-Oct-2004  01:13  2000.80.980.0    158,240  Svrnetcn.dll
x64 version
    Date        Time   Version        Size        File name
   -----------------------------------------------------------
   01-Oct-2004  02:28  2000.80.980.0      56,832  Dbmslpcn.dll
   01-Oct-2004  02:28  2000.80.980.0     185,856  Msgprox.dll
   19-May-2004  23:43  8.11.40517.0      722,944  Mssdi98.dll 
   01-Oct-2004  02:28  2000.80.980.0     151,040  Odsole70.dll
   01-Oct-2004  02:29  2000.80.980.0      27,136  Opends60.dll
   01-Oct-2004  02:28  2000.80.980.0     534,528  Replprov.dll
   01-Oct-2004  02:28  2000.80.980.0     769,024  Replrec.dll 
   30-Sep-2004  16:26  2000.80.980.0     146,432  Replres.rll
   01-Oct-2004  02:28  2000.80.980.0     650,240  Rinitcom.dll
   01-Oct-2004  02:28  2000.80.980.0     160,768  Semmap.dll
   01-Oct-2004  02:28  2000.80.980.0     132,608  Semnt.dll 
   01-Oct-2004  02:27  2000.80.980.0      10,240  Sqlagent.dll
   01-Oct-2004  02:28  2000.80.980.0      90,112  Sqlboot.dll 
   01-Oct-2004  02:28  2000.80.980.0      32,256  Sqlctr80.dll
   01-Oct-2004  02:28  2000.80.980.0  13,845,504  Sqldmo.dll 
   30-Sep-2004  16:15  2000.80.980.0      19,968  Sqlevn70.rll
   01-Oct-2004  02:28  2000.80.980.0      23,040  Sqlmap70.dll
   01-Oct-2004  02:28  2000.80.980.0     152,064  Sqlrepss.dll
   01-Oct-2004  02:28  2000.80.980.0     616,960  Sqlsort.dll 
   01-Oct-2004  02:28  2000.80.980.0     120,320  Sqlvdi.dll
   01-Oct-2004  02:28  2000.80.980.0     227,328  Sqsrvres.dll
   01-Oct-2004  02:28  2000.80.980.0      53,760  Ssmslpcn.dll
   01-Oct-2004  02:28  2000.80.980.0      59,904  Ssmsqlgc.dll
   01-Oct-2004  02:28  2000.80.980.0     255,488  Ssnetlib.dll
   01-Oct-2004  02:28  2000.80.980.0      20,992  Ssnmpn70.dll
   01-Oct-2004  02:28  2000.80.980.0     430,080  Svrnetcn.dll 
   01-Oct-2004  02:28  2000.80.980.0     183,296  Xplog70.dll
   01-Oct-2004  02:28  2000.80.980.0     187,392  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.

REFERENCES

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

MORE INFORMATION

The master.dbo.sp_restoredbreplication stored procedure cannot remove replication when the WITH KEEP_REPLICATION option of RESTORE DATABASE is not used. This is the default behavior.
Modification Type:MinorLast Reviewed:6/1/2006
Keywords:kbbug kbfix kbSQLServ2000preSP4fix kbHotfixServer kbQFE KB887974 kbAudDeveloper kbAudITPRO
©2004 Microsoft Corporation. All rights reserved.