SQL Server Q&A

Symptoms
After you install SQL Server 2000 Service Pack 3 (SP3), a query that uses a parallel plan may fail and cause an access violation in the ParallelPageSharedData::AddRef() function.
Resolution
Service pack informationTo 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?(http://support.microsoft.com/kb/290211/) How to obtain the latest SQL Server 2000 service pack
Hotfix informationThe 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.

DateTimeVersionSizeFile name——————————————————————31-May-200318:452000.80.818.078,400Console.exe25-Jun-200301:012000.80.818.033,340Dbmslpcn.dll25-Apr-200302:12786,432Distmdl.ldf25-Apr-200302:122,359,296Distmdl.mdf30-Jan-200301:55180Drop_repl_hotfix.sql23-Jun-200322:402000.80.837.01,557,052Dtsui.dll23-Jun-200322:402000.80.837.0639,552Dtswiz.dll24-Apr-200302:51747,927Instdist.sql03-May-200301:561,581Inst_repl_hotfix.sql08-Feb-200306:402000.80.765.090,692Msgprox.dll01-Apr-200302:071,873Odsole.sql05-Apr-200301:462000.80.800.062,024Odsole70.dll07-May-200320:412000.80.819.025,144Opends60.dll02-Apr-200321:482000.80.796.057,904Osql.exe02-Apr-200323:152000.80.797.0279,104Pfutil80.dll22-May-200322:5719,195Qfe469571.sql12-Jun-200316:371,083,989Replmerg.sql04-Apr-200321:532000.80.798.0221,768Replprov.dll08-Feb-200306:402000.80.765.0307,784Replrec.dll05-May-200300:051,085,874Replsys.sql01-Jun-200301:012000.80.818.0492,096Semobj.dll31-May-200318:272000.80.818.0172,032Semobj.rll29-May-200300:29115,944Sp3_serv_uni.sql01-Jun-200301:012000.80.818.04,215,360Sqldmo.dll07-Apr-200317:4425,172Sqldumper.exe19-Mar-200318:202000.80.789.028,672Sqlevn70.rll02-Jul-200300:182000.80.834.0180,736Sqlmap70.dll08-Feb-200306:402000.80.765.057,920Sqlrepss.dll23-Jun-200322:402000.80.837.07,553,105Sqlservr.exe08-Feb-200306:402000.80.765.045,644Sqlvdi.dll25-Jun-200301:012000.80.818.033,340Ssmslpcn.dll01-Jun-200301:012000.80.818.082,492Ssnetlib.dll01-Jun-200301:012000.80.818.025,148Ssnmpn70.dll01-Jun-200301:012000.80.818.0158,240Svrnetcn.dll31-May-200318:592000.80.818.076,416Svrnetcn.exe30-Apr-200323:522000.80.816.045,132Ums.dll02-Jul-200300:192000.80.834.098,816Xpweb70.dll Note Because offile dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Symptoms
This article describes the following about this hotfix release:The issues that are fixed by the hotfix packageThe prerequisites for installing the hotfix packageWhether you must restart the computer after you install the hotfix packageWhether the hotfix package is replaced by any other hotfix packageWhether you must make any registry changesThe files that are contained in the hotfix package
Resolution
When you run the DBCC MEMORYSTATUS statement in Microsoft SQL Server 2005, a minidump file is generated. Additionally, the following error message is logged in the SQL Server 2005 error log:

Date Time SPID ***Stack Dump being sent to T:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
Date Time SPID SqlDumpExceptionHandler: Process 128 generated fatal exception c0000094 EXCEPTION_INT_DIVIDE_BY_ZERO. SQL Server is terminating this process.
Date Time SPID *
Date Time SPID *
Date Time SPID * BEGIN STACK DUMP:
Date Time SPID * 07/27/07 09:55:00 spid 128
Date Time SPID *
Date Time SPID *
Date Time SPID * Exception Address = 0000000001911CC8
Module(sqlservr+0000000000911CC8)
Date Time SPID * Exception Code = c0000094
EXCEPTION_INT_DIVIDE_BY_ZERO

Symptoms
This article describes the following about this hotfix release:The issues that are fixed by the hotfix packageThe prerequisites for installing the hotfix packageWhether you must restart the computer after you install the hotfix packageWhether the hotfix package is replaced by any other hotfix packageWhether you must make any registry changesThe files that are contained in the hotfix package
Resolution
In Microsoft SQL Server 2005, when you call a method of a component object model (COM) object by using the sp_OAMethod stored procedure or the sp_OAGetProperty stored procedure, a memory leak occurs. For the sp_OAMethod stored procedure, this problem occurs if the method returns the result in the output parameter of the method. For the sp_OAGetProperty stored procedure, this problem occurs if the stored procedure returns a property value in the OUTPUT parameter.
Additionally, if the memory leaks exhausts the non-buffer pool memory region, the following error message is logged in the SQL Server error log file:

2008-05-01 08:35:07.80 spid535 Downgrading backup log buffers from 1024K to 64K
2008-05-06 09:35:22.55 spid77 Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE 1048576
2008-05-06 10:48:04.85 spid593 Error: 701, Severity: 17, State: 123.
2008-05-06 10:48:04.85 spid593 There is insufficient system memory to run this query.

Symptoms
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.The files that are contained in the hotfix package.
Resolution
When you open a database in Microsoft SQL Server 2000, you notice that a user database is marked as suspect. Also, an error message that is similar to the following is logged in the SQL Server 2000 error log:

<Date> <Time> spid9 Recovery of database ‘UserDatabaseName’ (5) is 2% complete (approximately 185 more seconds) (Phase 3 of 3).
<Date> <Time> spid9 Using ‘dbghelp.dll’ version ‘4.0.5′ *Dump thread – spid = 9, PSS = 0×80178098, EC = 0×801783c0
<Date> <Time> spid9 The exception information has been submitted to Watson error reporting.
<Date> <Time> spid9 Stack Signature for the dump is 0×986D5509
<Date> <Time> spid9 SQL Server Assertion: File: <page.cpp>, line=3430 Failed Assertion = ‘m_freeCnt + emptySlots * sizeof (Slot) >= spaceNeed’.
<Date> <Time> spid9 Location: page.cpp:3430 Expression: m_freeCnt + emptySlots * sizeof (Slot) >= spaceNeed

Symptoms
When you run a query in Microsoft SQL Server 2000 64-bit, you may experience an 8621 error condition. An 8621 error condition may cause the SQL Server 2000 64-bit program to close unexpectedly. When this problem occurs, the following messages are logged in the SQL Server error log:

2004-04-05 10:35:58.86 spid5104/05/04 10:35:58 Stack Overflow Dump not possible – Exception c00000fd E at 0×00000000007051E42004-04-05 10:35:58.86 spid51Address=7051e4 Exception Code = c00000fd2004-04-05 10:36:01.21 spid51<The query text follows.>…2004-04-05 10:37:07.82 spid512004-04-05 10:37:07.82 spid51TotalPhysicalMemory = 34349801472, AvailablePhysicalMemory = 70914375682004-04-05 10:37:07.82 spid51AvailableVirtualMemory = 7643227004928, AvailablePagingFile = 32936615936
This behavior has been observed in Microsoft SQL Server 2000 32-bit and in Microsoft SQL Server 2000 64-bit.
Resolution
Service pack informationTo 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
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.
SQL Server 2000 32-bit (x86)

DateTimeVersionSizeFile name————————————————————————-31-May-200318:452000.80.818.078,400Console.exe25-Mar-200422:272000.80.928.0315,968Custtask.dll30-Jan-200416:292000.80.911.033,340Dbmslpcn.dll25-Apr-200302:12786,432Distmdl.ldf25-Apr-200302:122,359,296Distmdl.mdf30-Jan-200301:55180Drop_repl_hotfix.sql12-Sep-200303:262000.80.859.01,905,216Dtspkg.dll26-Aug-200320:162000.80.854.0528,960Dtspump.dll23-Jun-200322:402000.80.837.01,557,052Dtsui.dll23-Jun-200322:402000.80.837.0639,552Dtswiz.dll24-Apr-200302:51747,927Instdist.sql03-May-200301:561,581Inst_repl_hotfix.sql30-Jan-200416:292000.80.911.090,692Msgprox.dll01-Apr-200302:071,873Odsole.sql30-Jan-200416:292000.80.911.062,024Odsole70.dll30-Jan-200416:292000.80.911.025,144Opends60.dll07-May-200318:47132,096Opends60.pdb30-Jan-200416:282000.80.911.057,904Osql.exe02-Apr-200323:152000.80.797.0279,104Pfutil80.dll04-Aug-200318:17550,780Procsyst.sql12-Sep-200300:3712,305Qfe469315.sql22-May-200322:5719,195Qfe469571.sql25-Mar-200421:031,104,848Replmerg.sql30-Jan-200416:292000.80.911.0221,768Replprov.dll30-Jan-200416:292000.80.911.0307,784Replrec.dll29-Jan-200423:242000.80.911.0159,813Replres.rll06-Sep-200300:001,087,150Replsys.sql13-Aug-200316:28986,603Repltran.sql30-Jan-200416:292000.80.911.0287,304Rinitcom.dll25-Mar-200422:272000.80.928.066,112Semmap.dll30-Jan-200416:292000.80.911.057,916Semnt.dll29-Jul-200320:132000.80.819.0492,096Semobj.dll31-May-200318:272000.80.818.0172,032Semobj.rll02-Jan-200419:422000.80.904.053,832Snapshot.exe09-Dec-200320:07117,834Sp3_serv_uni.sql05-Feb-200400:462000.80.913.028,672Sqlagent.dll05-Feb-200400:472000.80.913.0311,872Sqlagent.exe19-Feb-200418:022000.80.916.0168,001Sqlakw32.dll12-Mar-200404:342000.80.923.033,344Sqlctr80.dll30-Jan-200416:292000.80.911.04,215,360Sqldmo.dll07-Apr-200317:4425,172Sqldumper.exe29-Jan-200423:172000.80.911.028,672Sqlevn70.rll05-Mar-200417:132000.80.922.0180,792Sqlmap70.dll03-Sep-200302:562000.80.857.0188,992Sqlmmc.dll02-Sep-200323:032000.80.857.0479,232Sqlmmc.rll22-Oct-200300:082000.80.871.0401,984Sqlqry.dll30-Jan-200416:292000.80.911.057,920Sqlrepss.dll06-Apr-200420:062000.80.929.07,622,737Sqlservr.exe06-Apr-200420:0812,788,736Sqlservr.pdb30-Jan-200416:292000.80.911.0590,396Sqlsort.dll30-Jan-200416:292000.80.911.045,644Sqlvdi.dll30-Jan-200416:292000.80.911.0106,588Sqsrvres.dll30-Jan-200416:292000.80.911.033,340Ssmslpcn.dll30-Jan-200416:292000.80.911.082,492Ssnetlib.dll30-Jan-200416:292000.80.911.025,148Ssnmpn70.dll28-Oct-200304:212000.80.873.0123,456Stardds.dll30-Jan-200416:292000.80.911.0158,240Svrnetcn.dll30-Jan-200416:292000.80.911.076,416Svrnetcn.exe30-Apr-200323:522000.80.816.045,132Ums.dll30-Apr-200323:52132,096Ums.pdb30-Jan-200416:292000.80.911.098,872Xpweb70.dll
SQL Server 2000 64-bit (IA-64)

DateTimeVersionSizeFile name—————————————————————————16-Jul-200303:522000.80.818.056,832Dbmslpcn.dll03-May-200301:561,581Inst_repl_hotfix.sql11-Mar-200303:422000.80.782.0185,856Msgprox.dll16-Jul-200318:552000.80.818.0150,528Odsole70.dll16-Jul-200319:152000.80.818.0148,992Osql.exe26-Mar-200422:561,104,848Replmerg.sql11-Mar-200303:422000.80.782.0533,504Replprov.dll11-Mar-200303:422000.80.782.0767,488Replrec.dll27-Mar-200400:042000.80.928.0160,768Semmap.dll13-Mar-200408:072000.80.923.032,256Sqlctr80.dll01-Jun-200322:182000.80.818.0 13,845,504Sqldmo.dll16-Jul-200319:1339,936Sqldumper.exe11-Mar-200303:432000.80.782.023,040Sqlmap70.dll11-Mar-200303:432000.80.782.0152,064Sqlrepss.dll07-Apr-200415:422000.80.929.0 24,913,920Sqlservr.exe07-Apr-200415:4520,933,632Sqlservr.pdb11-Mar-200303:432000.80.782.0120,320Sqlvdi.dll16-Jul-200303:522000.80.818.053,760Ssmslpcn.dll01-Jun-200321:512000.80.818.0254,976Ssnetlib.dll02-Jun-200300:412000.80.818.020,992Ssnmpn70.dll01-Jun-200321:482000.80.818.0430,080Svrnetcn.dll01-Jun-200321:482000.80.818.0185,856Svrnetcn.exe31-Mar-200321:272000.80.778.0186,368Xpweb70.dllNoteBecause of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Symptoms
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 the 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.
Resolution
In Microsoft SQL Server 2000, when you run a query that generates many floating point exception errors, you may experience slow performance and query timeouts when you run other queries. This problem typically occurs when more than 1,000 floating point exceptions are generated.
Additionally, 17883 error reports that are similar to the following may be written to the SQL Server 2000 error log:

Error: 17883, Severity: 1, State: 0
Process 51:0 (dbc) UMS Context 0×018DA930 appears to be non-yielding on Scheduler 0. You may also receive one or more error messages that are similar to the following on a computer where a 64-bit version of SQL Server 2000 is installed:

Server: Msg 3628, Level 16, State 1, Line 2
A floating point exception occurred in the user process. Current transaction is canceledFor a list of all publicly released SQL Server 2000 Post-Service Pack 3a hotfixes, see the following article in the Microsoft Knowledge Base:
810185?(http://support.microsoft.com/kb/810185/) SQL Server 2000 hotfix update for SQL Server 2000 Service Pack 3 and 3a