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.
In Microsoft SQL Server 2005, you create a table-valued function in a database.
The database has the Auto Update Statistics database option set to true.
In the table-valued function, you use the INSERT INTO statement to insert data into the returned table variable.
You create a stored procedure in which you begin a snapshot isolation transaction that uses the table-valued function.
In this scenario, when you run the stored procedure, the stored procedure cannot finish its execution. You may have to restart the SQL Server service to recover from this issue.
If you use SQL Server Profiler to trace the execution, you see that the following error message is logged in the SQL trace:
Error: 3961, Severity: 16, State: 1
Snapshot isolation transaction failed in database 'tempdb' because the object accessed by the statement has been modified by a DDL statement in another concurrent transaction since the start of this transaction. It is disallowed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation.
Additionally, a minidump file is generated in the SQL Server 2005 log folder, and the following error messages are logged in the SQL Server 2005 Errorlog file:
Error message 1
Date Time SPID Deadlock encountered .... Printing deadlock information
Error message 2
Date Time SPID Deadlock monitor failed to resolve this deadlock.
This issue occurs because an unresolved deadlock occurs.
When the Auto Update Statistics database option is set to true, any out-of-date statistics are automatically updated on the database. In the scenario that is mentioned in the "Symptoms" section, a schema modification lock is generated on a temporary table. However, a schema stability lock has already been added on the table during the compiling process in the same working thread. Therefore, an unresolved deadlock occurs.
A 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:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
Prerequisites
SQL Server 2005 Service Pack 2
For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
913089
(http://support.microsoft.com/kb/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.
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.
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
(http://support.microsoft.com/kb/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
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Back to the top
