Microsoft KB Archive/931843

From BetaArchive Wiki

Article ID: 931843

Article Last Modified on 11/20/2007



APPLIES TO

  • Microsoft SQL Server 2005 Standard Edition
  • Microsoft SQL Server 2005 Developer Edition
  • Microsoft SQL Server 2005 Workgroup Edition
  • Microsoft SQL Server 2005 Enterprise Edition
  • Microsoft SQL Server 2005 Standard X64 Edition
  • Microsoft SQL Server 2005 Enterprise X64 Edition
  • Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
  • Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems



Bug #: 50000769 (SQL Hotfix)
Bug #: 501162 (SQLBUDT)

Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release.

SUMMARY

This article describes the following about this hotfix release:

  • The issues that are fixed by the 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


SYMPTOMS

Consider the following scenario:

  • In Microsoft SQL Server 2005, you have a stored procedure that creates a temporary table. The stored procedure also inserts data into the temporary table.
  • You do not run the stored procedure in an explicit transaction.
  • When you run the stored procedure, the stored procedure is stopped for one of the following reasons:
    • An exception occurs.
    • A server process ID (SPID) stops the process that runs the stored procedure.

In this scenario, SQL Server 2005 does not reclaim the disk space that is allocated to the temporary table. Additionally, you may receive one of the following error messages:

Error message 1


Error 1101: Could not allocate a new page for database 'tempdb' because of insufficient disk space in filegroup 'FilegroupName'. Create the necessary space by dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

Error message 2


Error 1105: Could not allocate space for object 'ObjectName' in database 'tempdb' because the 'FilegroupName' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

RESOLUTION

Cumulative update information

To resolve this problem, obtain the cumulative update package (build 3161) for SQL Server 2005 Service Pack 2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

935356 Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available


Hotfix information

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

You must have Microsoft SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix. For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005


Restart information

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

Registry information

You do not have to change the registry.

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 item in Control Panel.

SQL Server 2005 32-bit version
File name File version File size Date Time Platform
Databasemailengine.dll 9.0.2218.0 75,120 31-Jan-2007 16:48 x86
Logread.exe 2005.90.2218.0 400,752 31-Jan-2007 16:48 x86
Microsoft.analysisservices.adomdclient.dll 9.0.2218.0 546,160 31-Jan-2007 16:48 x86
Microsoft.analysisservices.deploymentengine.dll 9.0.2218.0 140,656 31-Jan-2007 16:48 x86
Microsoft.analysisservices.dll 9.0.2218.0 1,217,904 31-Jan-2007 16:48 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2218.0 78,192 31-Jan-2007 16:48 x86
Microsoft.sqlserver.sqlenum.dll 9.0.2218.0 910,704 31-Jan-2007 16:48 x86
Msasxpress.dll 9.0.2218.0 24,944 31-Jan-2007 16:48 x86
Msgprox.dll 2005.90.2218.0 200,560 31-Jan-2007 16:48 x86
Msmdlocal.dll 9.0.2218.0 15,645,552 31-Jan-2007 16:48 x86
Msmdredir.dll 9.0.2218.0 3,993,968 31-Jan-2007 16:48 x86
Mssqlsystemresource.ldf Not Applicable 524,288 30-Jan-2007 18:10 Not Applicable
Mssqlsystemresource.mdf Not Applicable 40,108,032 30-Jan-2007 18:10 Not Applicable
Qrdrsvc.exe 2005.90.2218.0 369,520 31-Jan-2007 16:48 x86
Rdistcom.dll 2005.90.2218.0 643,440 31-Jan-2007 16:48 x86
Repldp.dll 2005.90.2218.0 187,248 31-Jan-2007 16:48 x86
Replmerg.exe 2005.90.2218.0 320,880 31-Jan-2007 16:49 x86
Replprov.dll 2005.90.2218.0 550,256 31-Jan-2007 16:49 x86
Replrec.dll 2005.90.2218.0 784,752 31-Jan-2007 16:49 x86
Replsub.dll 2005.90.2218.0 407,408 31-Jan-2007 16:49 x86
Spresolv.dll 2005.90.2218.0 177,008 31-Jan-2007 16:49 x86
Sqlaccess.dll 2005.90.2218.0 350,576 31-Jan-2007 16:49 x86
Sqlagent90.exe 2005.90.2218.0 321,392 31-Jan-2007 16:49 x86
Sqlservr.exe 2005.90.2218.0 28,977,064 31-Jan-2007 16:49 x86
Sysdbupg.sql Not Applicable 218,486 29-Dec-2006 13:53 Not Applicable
Xmlsub.dll 2005.90.2218.0 195,440 31-Jan-2007 16:49 x86
Xpstar90.dll 2005.90.2218.0 295,280 31-Jan-2007 16:49 x86
Xpstar90.rll 2005.90.2218.0 155,504 31-Jan-2007 16:49 x86
SQL Server 2005 x64-based version
File name File version File size Date Time Platform
Databasemailengine.dll 9.0.2218.0 75,120 31-Jan-2007 00:17 x86
Logread.exe 2005.90.2218.0 525,168 31-Jan-2007 00:18 x64
Microsoft.analysisservices.adomdclient.dll 9.0.2218.0 546,160 31-Jan-2007 16:48 x86
Microsoft.analysisservices.adomdclient.dll 9.0.2218.0 546,160 31-Jan-2007 00:18 x86
Microsoft.analysisservices.deploymentengine.dll 9.0.2218.0 140,656 31-Jan-2007 16:48 x86
Microsoft.analysisservices.dll 9.0.2218.0 1,217,904 31-Jan-2007 16:48 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2218.0 78,192 31-Jan-2007 16:48 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2218.0 94,064 31-Jan-2007 00:18 x64
Microsoft.sqlserver.sqlenum.dll 9.0.2218.0 877,936 31-Jan-2007 00:18 x86
Msasxpress.dll 9.0.2218.0 24,944 31-Jan-2007 16:48 x86
Msasxpress.dll 9.0.2218.0 30,064 31-Jan-2007 00:18 x64
Msgprox.dll 2005.90.2218.0 262,000 31-Jan-2007 00:18 x64
Msmdlocal.dll 9.0.2218.0 15,645,552 31-Jan-2007 16:48 x86
Msmdredir.dll 9.0.2218.0 3,993,968 31-Jan-2007 16:48 x86
Mssqlsystemresource.ldf Not Applicable 524,288 30-Jan-2007 18:10 Not Applicable
Mssqlsystemresource.mdf Not Applicable 40,108,032 30-Jan-2007 18:10 Not Applicable
Qrdrsvc.exe 2005.90.2218.0 434,032 31-Jan-2007 00:18 x64
Rdistcom.dll 2005.90.2218.0 836,464 31-Jan-2007 00:18 x64
Repldp.dll 2005.90.2218.0 187,248 31-Jan-2007 16:48 x86
Repldp.dll 2005.90.2218.0 237,936 31-Jan-2007 00:18 x64
Replmerg.exe 2005.90.2218.0 417,648 31-Jan-2007 00:18 x64
Replprov.dll 2005.90.2218.0 747,888 31-Jan-2007 00:18 x64
Replrec.dll 2005.90.2218.0 1,011,056 31-Jan-2007 00:18 x64
Replsub.dll 2005.90.2218.0 528,240 31-Jan-2007 00:18 x64
Spresolv.dll 2005.90.2218.0 225,648 31-Jan-2007 00:18 x64
Sqlaccess.dll 2005.90.2218.0 357,744 31-Jan-2007 00:18 x86
Sqlagent90.exe 2005.90.2218.0 392,560 31-Jan-2007 00:18 x64
Sqlservr.exe 2005.90.2218.0 39,406,960 31-Jan-2007 00:18 x64
Sysdbupg.sql Not Applicable 218,486 29-Dec-2006 13:53 Not Applicable
Xmlsub.dll 2005.90.2218.0 319,856 31-Jan-2007 00:18 x64
Xpstar90.dll 2005.90.2218.0 543,600 31-Jan-2007 00:18 x64
Xpstar90.rll 2005.90.2218.0 156,016 31-Jan-2007 00:18 x64
SQL Server 2005 Itanium architecture version
File name File version File size Date Time Platform
Databasemailengine.dll 9.0.2218.0 75,120 31-Jan-2007 00:20 x86
Logread.exe 2005.90.2218.0 1,098,096 31-Jan-2007 00:20 IA-64
Microsoft.analysisservices.adomdclient.dll 9.0.2218.0 546,160 31-Jan-2007 16:48 x86
Microsoft.analysisservices.adomdclient.dll 9.0.2218.0 546,160 31-Jan-2007 00:20 x86
Microsoft.analysisservices.deploymentengine.dll 9.0.2218.0 140,656 31-Jan-2007 16:48 x86
Microsoft.analysisservices.dll 9.0.2218.0 1,217,904 31-Jan-2007 16:48 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2218.0 78,192 31-Jan-2007 16:48 x86
Microsoft.sqlserver.mgdsqldumper.dll 2005.90.2218.0 165,744 31-Jan-2007 00:20 IA-64
Microsoft.sqlserver.sqlenum.dll 9.0.2218.0 877,936 31-Jan-2007 00:20 x86
Msasxpress.dll 9.0.2218.0 24,944 31-Jan-2007 16:48 x86
Msasxpress.dll 9.0.2218.0 57,712 31-Jan-2007 00:20 IA-64
Msgprox.dll 2005.90.2218.0 545,136 31-Jan-2007 00:20 IA-64
Msmdlocal.dll 9.0.2218.0 48,717,168 31-Jan-2007 00:20 IA-64
Msmdredir.dll 9.0.2218.0 6,249,328 31-Jan-2007 00:20 IA-64
Mssqlsystemresource.ldf Not Applicable 524,288 30-Jan-2007 18:10 Not Applicable
Mssqlsystemresource.mdf Not Applicable 40,108,032 30-Jan-2007 18:10 Not Applicable
Qrdrsvc.exe 2005.90.2218.0 943,984 31-Jan-2007 00:20 IA-64
Rdistcom.dll 2005.90.2218.0 1,884,016 31-Jan-2007 00:20 IA-64
Repldp.dll 2005.90.2218.0 187,248 31-Jan-2007 16:48 x86
Repldp.dll 2005.90.2218.0 511,344 31-Jan-2007 00:20 IA-64
Replmerg.exe 2005.90.2218.0 957,296 31-Jan-2007 00:20 IA-64
Replprov.dll 2005.90.2218.0 1,619,824 31-Jan-2007 00:20 IA-64
Replrec.dll 2005.90.2218.0 2,144,112 31-Jan-2007 00:20 IA-64
Replsub.dll 2005.90.2218.0 1,159,536 31-Jan-2007 00:20 IA-64
Spresolv.dll 2005.90.2218.0 498,032 31-Jan-2007 00:20 IA-64
Sqlaccess.dll 2005.90.2218.0 352,112 31-Jan-2007 00:20 x86
Sqlagent90.exe 2005.90.2218.0 1,143,664 31-Jan-2007 00:20 IA-64
Sqlservr.exe 2005.90.2218.0 72,436,592 31-Jan-2007 00:20 IA-64
Sysdbupg.sql Not Applicable 218,486 29-Dec-2006 13:53 Not Applicable
Xmlsub.dll 2005.90.2218.0 593,264 31-Jan-2007 00:20 IA-64
Xpstar90.dll 2005.90.2218.0 953,712 31-Jan-2007 00:20 IA-64
Xpstar90.rll 2005.90.2218.0 154,992 31-Jan-2007 00:20 IA-64


WORKAROUND

To work around this problem, use one of the following methods.

Method 1

In the stored procedure, use a table variable instead of the temporary table.

For example, you have the following statement in the stored procedure.

CREATE TABLE #tab (id INT, a CHAR(80))

Instead, use the following statement.

DECLARE @tab TABLE (id INT, a CHAR(80))

Method 2

Run the stored procedure in an explicit transaction.

For example, you have the MySP stored procedure. Use the following statements to run the MySP stored procedure.

BEGIN TRANS
EXEC MySP
COMMIT

Method 3

In the stored procedure, perform the operations on the temporary table in an explicit transaction.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

If you know the reason that the stored procedure is stopped, you can prevent the stored procedure from being stopped by using a SET statement. Therefore, SQL Server 2005 reclaims the disk space that is allocated to the temporary table.

For example, you can prevent the stored procedure from being stopped by using one of the following SET statements:

  • SET XACT_ABORT OFF
  • SET ARITHABORT OFF

You can run the following statement to obtain the number of pages that are allocated by the temporary objects in the tempdb database in SQL Server 2005.

SELECT Name=so.name, TotalPages=total_pages
FROM tempdb.sys.objects so (NOLOCK)
JOIN tempdb.sys.partitions pa (nolock) ON so.object_id = pa.object_id
    LEFT JOIN tempdb.sys.allocation_units al (NOLOCK)
    ON (al.type in (1, 3) AND pa.hobt_id = al.container_id)
    OR (al.type = 2 AND pa.partition_id = al.container_id)
WHERE name LIKE '#%'
ORDER BY Name

In the result that this statement returns, many objects in the Name column may have a value that is greater than 0 in the TotalPages column. In this case, you experience this problem.

Note If an object has 0 in the TotalPages column, the object is a cached object. A cached object is truncated instead of deleted. This behavior has the following benefits:

  • The metadata of the cached object is cached.
  • The risk of contention in the tempdb database is reduced.


REFERENCES

For more information about how to plan for the capacity of the tempdb database, visit the following Microsoft Developer Network (MSDN) Web site:

For more 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 more information about software update terminology, 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: kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver KB931843