Article ID: 2638448 - Last Review: April 12, 2012 - Revision: 4.0

FIX: Access violation when a query is compiled or recompiled in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

Microsoft distributes Microsoft SQL Server 2008 SP2, Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 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 SP2, SQL Server 2008 R2 or SQL Server 2012 fix release.

Back to the top

SYMPTOMS

When a query is being compiled or recompiled in Microsoft SQL Server 2008, in Microsoft SQL Server 2008 R2 or in Microsoft SQL Server 2012, an access violation occurs in the TDelayedPartitionedStack::GetNumberOfPartitions function. Additionally, a memory dump file is created.

Back to the top

RESOLUTION

Cumulative update information

SQL Server 2012

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2679368 (http://support.microsoft.com/kb/2679368/LN/ ) Cumulative update package 1 for SQL Server 2012

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 2012 fix release. Microsoft recommends 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:

2692828 (http://support.microsoft.com/kb/2692828/LN/ ) The SQL Server 2012 builds that were released after SQL Server 2012 was released

You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.

SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 3 for SQL Server 2008 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2648098 (http://support.microsoft.com/kb/2648098/LN/ ) Cumulative update package 3 for SQL Server 2008 Service Pack 3

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. Microsoft recommends 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:

2629969 (http://support.microsoft.com/kb/2629969/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released

Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 11. 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:

2633145 (http://support.microsoft.com/kb/2633145/ ) Cumulative Update package 11 for SQL Server 2008 R2

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:

981356 (http://support.microsoft.com/kb/981356/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2633146 (http://support.microsoft.com/kb/2633146/ ) Cumulative Update package 4 for SQL Server 2008 R2 Service Pack 1

2567616 (http://support.microsoft.com/kb/2567616/ ) The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 Service Pack 2 (SP2) cumulative update package 7

The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

2617148 (http://support.microsoft.com/kb/2617148/ ) Cumulative update package 7 for SQL Server 2008 Service Pack 2

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 Service Pack 2 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:

2402659 (http://support.microsoft.com/kb/2402659/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released

Back to the top