FIX: Memory leak occurs when an application that uses SQL Server Native Client tries to connect and close the connection to a SQL Server 2008 R2 instance

Article translations Article translations
Article ID: 2912049 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You have an application that uses Microsoft SQL Server Native Client in SQL Server 2008 R2.
  • The application tries to connect to an instance of SQL Server.
  • Perform some actions, then close the connection.
In this scenario, memory leak may occur.
Note The memory leak occurs on the lsass.exe handle.

Resolution

The issue was first fixed in the following cumulative update of SQL Server.

Cumulative Update 11 for SQL Server 2008 R2 SP2

About cumulative updates for SQL Server

Collapse this imageExpand this image
assets folding start collapsed
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Collapse this imageExpand this image
assets folding end collapsed

Status

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

Properties

Article ID: 2912049 - Last Review: February 18, 2014 - Revision: 1.0
Applies to
  • Microsoft SQL Server 2008 R2 Service Pack 2, when used with:
    • Microsoft SQL Server 2008 R2 Developer
    • Microsoft SQL Server 2008 R2 Enterprise
    • Microsoft SQL Server 2008 R2 Standard
Keywords: 
kbqfe kbfix kbsurveynew kbexpertiseadvanced KB2912049

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com