Article ID: 916086 - View products that this article applies to.
BUG #: 518 (SQL Hotfix)
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.
This article describes the following about this hotfix release:
When you create and then drop many temporary tables in Microsoft SQL Server 2005, errors may be generated in the tempdb database. When this problem occurs, the following error messages may be logged in the SQL Server Errorlog file:
Error: 605, Severity: 21, State: 3. Attempt to fetch logical page (1:584) in database 2 failed. It belongs to allocation unit 445237904015360 not to 72057594060079104.
Error: 3316, Severity: 21, State: 1. During undo of a logged operation in database 'tempdb', an error occurred at log record ID (49:16:7). The row was not found. Restore the database from a full backup, or repair the database.
When error 605 and error 3316 are generated, both the following error messages may also be logged in the SQL Server Errorlog file:
Error: 5243, Severity: 22, State: 1. An inconsistency was detected during an internal operation. Please contact technical support. Reference number 8.
Error: 3314, Severity: 21, State: 4. During undoing of a logged operation in database 'tempdb', an error occurred at log record ID (49:16:12). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database.
Additionally, when error 605 and error 3316 are generated, the SQL Server service stops.
Error: 3449, Severity: 21, State: 1. SQL Server must shut down in order to recover a database (database ID 2). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database.
Service pack informationTo resolve this problem, obtain the latest service pack for SQL Server 2005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/913089/ )How to obtain the latest service pack for SQL Server 2005
Hotfix informationA supported hotfix is 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 software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
PrerequisitesThere are no prerequisites for this hotfix.
Restart informationYou do not have to restart your computer after you apply this hotfix. However, you must restart the SQL Server service to enable the changes that this hotfix provides.
Registry informationYou do not have to create any registry keys or modify any registry keys to use any hotfixes that this package contains.
Hotfix file informationThis hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that this article lists.
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 x86 versions
Collapse this tableExpand this table
To work around this problem, use one of the following methods.
Method 1: Use permanent tablesUse permanent tables in user databases instead of using temporary tables in the tempdb database.
Method 2: Disable the Auto Update Statistics option and the Auto Create Statistics optionDisable the Auto Create Statistics option and the Auto Update Statistics option in the tempdb database. For more information about SQL Server 2005 query optimizer statistics, visit the following Microsoft TechNet Web site:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 916086 - Last Review: October 9, 2011 - Revision: 3.0
Contact us for more help
Connect with Answer Desk for expert help.