FIX: Memory Leak in MDAC SQLOLEDB Provider on SERVERDATAONINSERT and Column Size That Is Larger Than 255 (302995)
The information in this article applies to:
- Microsoft Data Access Components 2.1
- Microsoft Data Access Components 2.1 (GA)
- Microsoft Data Access Components 2.1 SP1
- Microsoft Data Access Components 2.1 SP2
- Microsoft Data Access Components 2.5
- Microsoft Data Access Components 2.5 SP1
- Microsoft Data Access Components 2.5 SP2
- Microsoft Data Access Components 2.6
This article was previously published under Q302995 SYMPTOMS
A memory leak occurs in Microsoft OLE DB Provider for SQL Server (SQLOLEDB) with SERVERDATAONINSERT when the column size is larger than 255.
RESOLUTION To resolve this problem, obtain the latest service pack for Microsoft MDAC 2.5. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 293312INFO: How to Obtain the Latest MDAC 2.5 Service Pack You may also resolve this problem by obtaining the latest service pack for SQL Server 2000, the latest service pack for MDAC 2.6, or the hotfix referenced below.
For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack
For additional information, click the article number below
to view the article in the Microsoft Knowledge Base:
300635 INFO: How to Obtain the Latest MDAC 2.6 Service Pack
HotfixMDAC 2.5
The English version of this fix should have the following file attributes or later:
Date Version Size File name Platform
-------------------------------------------------------------
04-Jun-2001 7.1.9.99 545,040 bytes Sqloledb.dll x86
MDAC 2.6
The English version of this fix should have the following file attributes or later:
Date Version Size File name Platform
------------------------------------------------------------------
11-Jun-2001 2000.80.301.0 491,584 bytes Sqloledb.dll x86
11-Jun-2001 2000.80.301.0 61,440 bytes Sqloledb.dll x86
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft MDAC 2.5 Service Pack 3. This problem was first corrected in SQL Server 2000 Service Pack 2 and MDAC 2.6 Service Pack 2.
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbMDAC250SP3fix kbbug kbfix kbmdac260sp2fix kbSQLServ2000preSP2Fix KB302995 |
---|
|