Article ID: 2506235 - Last Review: October 17, 2011 - Revision: 6.0

FIX: An access violation may occur when a database is enabled for Transparent Database Encryption in SQL Server 2008 or in SQL Server 2008 R2

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 or Microsoft 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 Page

Expand all | Collapse all

SYMPTOMS

An access violation may occur if one of the following conditions is true:
  • You use the sp_configure Transact-SQL command to configure nondefault values for the affinity I/O or affinity64 I/O mask and then try to enable Transparent Database Encryption for a database.
  • You try to back up a database that is enabled for Transparent Database Encryption.
Back to the top

CAUSE

This issue occurs because of an incorrect synchronization between the SQL Server threads when the Database Encryption key (DEK) that is used for Transparent Database Encryption is accessed.
Back to the top

RESOLUTION

Cumulative update information

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 3 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:
2591748  (http://support.microsoft.com/kb/2591748/ ) Cumulative Update package 3 for SQL Server 2008 R2 Service Pack 1
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:
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 R2

The fix for this issue was first released in Cumulative Update 9. 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:
2567713  (http://support.microsoft.com/kb/2567713/ ) Cumulative Update package 9 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 Service Pack 2

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2527180  (http://support.microsoft.com/kb/2527180/LN/ ) Cumulative update package 4 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 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/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
Back to the top

SQL Server 2008

The fix for this issue was first released in Cumulative Update 13 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:
2497673  (http://support.microsoft.com/kb/2497673/LN/ ) Cumulative update package 13 for SQL Server 2008 Service Pack 1
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:
970365  (http://support.microsoft.com/kb/970365/LN/ ) The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
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.
Back to the top

WORKAROUND

  • If you encounter the access violation when you are performing the backup of the database, you can issue a manual CHECKPOINT before you back up the database.
  • If you notice the access violation when the affinity I/O or affinity64 I/O mask is enabled, you can consider setting the values for the affinity I/O or affinity64 I/O mask to their default setting.
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top

MORE INFORMATION

The following table provides more information about the products or tools that automatically check for this condition on your instance of SQL Server and about the versions of SQL Server against which the rule is evaluated.
Collapse this tableExpand this table
Rule softwareRule titleRule descriptionProduct versions against which the rule is evaluated
System Center AdvisorSQL Server missing update 2506235 to enable correct I/O processing for encrypted databases on hidden schedulersSystem Center Advisor determines whether the instance of SQL Server has any databases that are enabled for Transparent Database Encryption (TDE), whether the affinity I/O mask settings are nondefault values, and whether required SQL Server updates are installed. If the instance of SQL Server does not have the required updates that are mentioned in this article, and if this instance has one or more databases that are enabled for TDE, System Center Advisor generates a warning for this instance of SQL Server. Review the information that is provided in the "Information Collected" section of the advisor warning, and then use the resolutions that are provided in this article.SQL Server 2008, SQL Server 2008 R2
()
Back to the top

REFERENCES

For more information about TDE, visit the following MSDN website:
General information about TDE (http://msdn.microsoft.com/en-us/library/bb934049(v=SQL.100).aspx)
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897  (http://support.microsoft.com/kb/935897/ ) An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
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
APPLIES TO
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Express
  • Microsoft SQL Server 2008 Express with Advanced Services
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Express
  • Microsoft SQL Server 2008 R2 Express with Advanced Services
Back to the top
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2506235
Back to the top