Symptoms
Consider the following scenario:
-
You have a SQL Server Native Client OLE DB provider application that connects to a server that is running Microsoft SQL Server 2012 or SQL Server 2014 to access data.
-
The application calls the Prepare method on an instance of SQL Server to prepare queries to use parameters.
In this scenario, a memory leak condition may occur.
Resolution
The issue was first fixed in the following cumulative update of SQL Server.
Cumulative Update 1 for SQL Server 2014 /en-us/help/2931693
Cumulative Update 7 for SQL Server 2012 SP1 /en-us/help/2894115
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:
Workaround
To work around this problem, add the DataTypeCompatibility=80 keyword to the Connection String for the SQL Server.For more information, see Data Type Compatibility for Client Versions in the following topic on the Microsoft TechNet website:
System Requirements for SQL Server Native Client
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
See the terminology Microsoft uses to describe software updates.
