Select the product you need help with
FIX: An assertion failure occurs when you run a parameterized query that has many parameters in SQL Server 2008 or SQL Server 2008 R2 and that has the SHOWPLAN_XML option enabledArticle ID: 981922 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2008 or SQL Server 2008 R2 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 2008 or SQL Server 2008 R2 fix release. On This PageSYMPTOMSIn Microsoft SQL Server 2008 or SQL Server 2008 R2 , you set the SHOWPLAN_XML option to ON. When you run a parameterized query that has many parameters, an assertion failure occurs. For example, an assertion failure occurs when you run a parameterized query that has more than 500 parameters. Additionally, you receive the following error message: Location:. showplanxml.cpp:2312.Expression:. usTemp < e_snMax.SPID:.. <ID>.Process ID:. <ID>
<Date Time> spid<ID> Error: 17066, Severity: 16, State: 1.
<Date Time> spid<ID> SQL Server Assertion: File: <showplanxml.cpp>, line=2312 Failed Assertion = 'usTemp < e_snMax'. This error may be timing- related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted. <Date Time> spid<ID> Error: 3624, Severity: 20, State: 1. <Date Time> spid<ID> A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support. CAUSEThis problem occurs because of an offset issue in the SHOWPLAN compact format that is used by the SHOWPLAN_XML option. RESOLUTIONCumulative update informationSQL Server 2008 R2The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base: 2072493 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/2072493/
)
Cumulative update package 2 for SQL Server 2008 R2981356
(http://support.microsoft.com/kb/981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was releasedSQL Server 2008The fix for this issue was first released in Cumulative Update 8 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:981702 Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/981702/LN/
)
Cumulative update package 8 for SQL Server 2008 Service Pack 1970365
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/970365/LN/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. REFERENCESFor information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897 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:
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
822499 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/822499/
)
New naming schema for Microsoft SQL Server software update packages824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 981922 - Last Review: June 23, 2010 - Revision: 2.0 APPLIES TO
|
Back to the top
