Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Private bytes keep increasing when you encrypt data on SQL Server on Windows 10, version 1607, Windows Server 2016, Window 8.1 or Windows Server 2012 R2


View products that this article applies to.

This article describes an issue when you encrypt data on Microsoft SQL Server on Windows 10, version 1607, Windows Server 2016, Window 8.1 or Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

↑ Back to the top


Symptoms

Assume that you encrypt data on a SQL Server that is running on Windows 10, version 1607, Windows Server 2016, Window 8.1, Windows RT 8.1, or Windows Server 2012 R2. Multiple open key operations occur in one SQL Server connection. In this situation, you notice that the Private (KB) and Working Set (KB) columns for SQL Server keep increasing in the Resource Monitor.

↑ Back to the top


Cause

This issue occurs because of an issue inside the rsaenh.dll file, version 6.3.9600.16384. SQL Server internally uses Cryptography Next Generation (CNG) functions to manage data encryption. If you use the VMMAP tool, take an analysis of the process or collect Xperf data with heap tracing, you would see that most memory consumption is accounted from the default heap. 
This issue would only occur if in SQL Server if you use data encryption by using a symmetric key that uses a certificate, and then you execute queries that open and close the symmetric key in a recursive loop on a Windows Server 2016 or Windows Server 2012 R2-based computer. 

↑ Back to the top


Resolution

To resolve this issue for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2, install update rollup 2975719, or get the standalone package for this update tbhrough the Microsoft Update Catalog website.

To resolve this issue for Windows 10, version 1607 or Windows Server 2016, install update rollup 4284833.

Update information

Prerequisites

To apply this update for Windows 8.1, Windows RT 8.1, or Windows Server 2012 R2, you must first install the update 2919355. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update: April 2014

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You have to restart the computer after you apply this update.

Update replacement information

This update does not replace a previously released update.

File information

 

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
 
Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 file information notes
Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
     
    Version Product Milestone Service branch
    6.3.960 0.17 xxx Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 RTM GDR
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For Windows 10, Version 1607 and Windows Server 2016

For a list of the files that are provided in this update, download the file information for cumulative update 4284833.

For Windows RT 8.1
File name File version File size Date Time Platform
Rsaenh.dll 6.3.9600.17200 165,824 07-Jun-2014 10:06 Not applicable
For all supported x86-based versions of Windows 8.1
File name File version File size Date Time Platform
Rsaenh.dll 6.3.9600.17200 189,016 07-Jun-2014 10:20 x86
For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File name File version File size Date Time Platform
Rsaenh.dll 6.3.9600.17200 216,368 07-Jun-2014 12:46 x64
Rsaenh.dll 6.3.9600.17200 189,016 07-Jun-2014 10:20 x86

↑ Back to the top


Workaround

To work around this issue, encrypt the SYMMETRIC key by using a password instead of a certificate.

↑ 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

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information

Additional file information for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

Additional files for Windows RT 8.1
File propertyValue
File nameArm_09dd58757800de51b3c5310c5b3922b3_31bf3856ad364e35_6.3.9600.17201_none_59cfebc2519c83cc.manifest
File versionNot applicable
File size698
Date (UTC)09-Jun-2014
Time (UTC)17:03
PlatformNot applicable
File nameArm_microsoft-windows-rsaenh-dll_31bf3856ad364e35_6.3.9600.17201_none_f4bcac7acc9d1dc5.manifest
File versionNot applicable
File size2,617
Date (UTC)07-Jun-2014
Time (UTC)11:11
PlatformNot applicable
Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_9dcb6de35b79d4c35c2bbaeb31b3559e_31bf3856ad364e35_6.3.9600.17201_none_b28f8a3e24abb79c.manifest
File versionNot applicable
File size698
Date (UTC)09-Jun-2014
Time (UTC)16:14
PlatformNot applicable
File nameX86_microsoft-windows-rsaenh-dll_31bf3856ad364e35_6.3.9600.17201_none_f4ba3a22cc9ffeff.manifest
File versionNot applicable
File size2,617
Date (UTC)07-Jun-2014
Time (UTC)10:43
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File propertyValue
File nameAmd64_9dcb6de35b79d4c35c2bbaeb31b3559e_31bf3856ad364e35_6.3.9600.17201_none_0eae25c1dd0928d2.manifest
File versionNot applicable
File size700
Date (UTC)09-Jun-2014
Time (UTC)17:10
PlatformNot applicable
File nameAmd64_dbf4f750b16b2ab5f215db3f98fa3563_31bf3856ad364e35_6.3.9600.17201_none_6ae995bb3e5f63b1.manifest
File versionNot applicable
File size702
Date (UTC)09-Jun-2014
Time (UTC)17:10
PlatformNot applicable
File nameAmd64_microsoft-windows-rsaenh-dll_31bf3856ad364e35_6.3.9600.17201_none_50d8d5a684fd7035.manifest
File versionNot applicable
File size2,621
Date (UTC)07-Jun-2014
Time (UTC)13:11
PlatformNot applicable
File nameX86_microsoft-windows-rsaenh-dll_31bf3856ad364e35_6.3.9600.17201_none_f4ba3a22cc9ffeff.manifest
File versionNot applicable
File size2,617
Date (UTC)07-Jun-2014
Time (UTC)10:43
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbqfe

↑ Back to the top

Article Info
Article ID : 2975620
Revision : 4
Created on : 9/4/2018
Published on : 9/4/2018
Exists online : False
Views : 292