BUG: Memory Leak in OLE DB Provider for SQL Server When It Is Loaded and Unloaded Multiple Times (294168)
The information in this article applies to:
- Microsoft Data Access Components 2.5
- Microsoft Data Access Components 2.6
This article was previously published under Q294168 SYMPTOMS You may see a memory leak when repeatedly loading and
unloading the Microsoft OLE DB provider for SQL Server (SQLOLEDB) and
connecting to a Microsoft SQL Server database. You may see the same behavior
when using the Microsoft OLE DB provider for ODBC drivers (MSDASQL) with the
SQL Server ODBC driver. CAUSE This is caused by a slight memory leak in the OLE DB
implementation support routines (Msdatl2.dll or Msdatl3.dll). RESOLUTION To work around this problem, keep a global connection alive
or have the COM library initialized in the main thread.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft
products that are listed at the beginning of this article.
This problem was corrected in MDAC 2.7, and MDAC 2.5 Service
Pack 3 (SP3). There is also a hotfix available for this
problem.
For additional
information about this hotfix, click the article number below to view the
article in the Microsoft Knowledge Base: 312575 FIX: Virtual Memory Leak with Large Number of Concurrently Open Recordsets
Modification Type: | Major | Last Reviewed: | 4/6/2004 |
---|
Keywords: | kbbug kbfix KB294168 |
---|
|