FIX: SMO handle leak when the ConnectionInfo object is called by using user impersonation in SQL Server 2012

Applies to: SQL Server 2012 EnterpriseSQL Server 2012 Business IntelligenceSQL Server 2012 Developer

Microsoft SQL Server 2012 Service Pack 1 fixes have been released as one downloadable file. Given that the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2012 Service Pack 1 fix release.

Symptoms


When you have code that accesses the ConnectionInfo object from the SQL Server Management Objects (SMO) by using user impersonation, the resource is not released. Therefore, the number of allocated handles increases quickly, specifically, Semaphone handles, Token handles and Event handles. This may cause SQL Server Management Studio to fail. Additionally, this may cause SQL Server Data Engine to fail if SMO calls occur on the same computer.

Resolution


Cumulative update information

Cumulative Update 4 for SQL Server 2012 SP1

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to go to the article in the Microsoft Knowledge Base:
2833645 Cumulative update 4 for SQL Server 2012 SP1
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 SP1 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 go to the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Status


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

References


For more information about the Incremental Servicing Model for SQL Server, click the following article number to go to the article in the Microsoft Knowledge Base:
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 go to the article in the Microsoft Knowledge Base:
822499 Naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to go to the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates