Select the product you need help with
FIX: Access violation when you use Database Engine Tuning Advisor to tune a table in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012 if you enable the "Include filtered indexes" check boxArticle ID: 2713151 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2008 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 fix release. On This PageSymptomsConsider the following scenario:
Tuning Process exited unexpectedly (DTAEngine) Note When this issue occurs, a minidump file is generated in the SQL Server log folder. ResolutionCumulative update informationCumulative update package 1 for SQL Server 2012 Service Pack 1The fix for this issue was first released in Cumulative Update 1. For more information about how to obtain this cumulative update package for SQL Server 2012 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:2765331 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. 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/2765331/
)
Cumulative update package 1 for SQL Server 2012 Service Pack 12772858
(http://support.microsoft.com/kb/2772858/
)
The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was releasedSQL Server 2008 R2 Service Pack 2The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 R2 Service Pack 2. 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:2740411 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/2740411/
)
Cumulative Update package 2 for SQL Server 2008 R2 Service Pack 22730301
(http://support.microsoft.com/kb/2730301/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released SQL Server 2008 R2 Service Pack 1The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:2723743 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 Service Pack 1 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/2723743/
)
Cumulative update package 8 for SQL Server 2008 R2 SP12567616
(http://support.microsoft.com/kb/2567616/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 SP1 was releasedSQL Server 2012The fix for this issue was first released in Cumulative Update 3 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:2723749 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:
(http://support.microsoft.com/kb/2723749/LN/
)
Cumulative update package 3 for SQL Server 20122692828 You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.
(http://support.microsoft.com/kb/2692828/LN/
)
The SQL Server 2012 builds that were released after SQL Server 2012 was released Cumulative update package 6 for SQL Server 2008 SP 3The fix for this issue was first released in Cumulative Update 6. For more information about how to obtain this cumulative update package for SQL Server 2008 SP3, click the following article number to view the article in the Microsoft Knowledge Base:2715953 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 SP3 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/2715953/
)
Cumulative update package 6 for SQL Server 2008 SP32629969
(http://support.microsoft.com/kb/2629969/
)
SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was releasedStatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. ReferencesFor more information about Database Engine Tuning Advisor, go to the following MSDN website: General information about Database Engine Tuning Advisor For more information the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
(http://msdn.microsoft.com/en-us/library/ms188639(v=sql.100).aspx)
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/
)
Naming schema for Microsoft SQL Server software update packages 824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates PropertiesArticle ID: 2713151 - Last Review: November 20, 2012 - Revision: 4.0 Applies to
|  |
Back to the top
