Dale, could this be the bug we're having?
FIX: Memory Leak with DB-Library Connection Using TCP/IP or IPX/SPX
--------------------------------------------------------------------------------
The information in this article applies to:
Microsoft SQL Server version 7.0
--------------------------------------------------------------------------------
BUG #: 55725 (SQLBUG_70)
SYMPTOMS
A memory leak can occur after opening a DB-Library connection when the
application is using the TCP/IP or IPX/SPX network libraries. This leak persists
for each connection to SQL Server through DB-Library even after the connection
is closed.
RESOLUTION
A supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next SQL Server
service pack that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services
to obtain the fix. For a complete list of Microsoft Product Support Services
phone numbers and information on support costs, please go to the following
address on the World Wide Web:
http://www.microsoft.com/support/supportnet/overview/overview.asp
The English version of this fix should have the following file attributes or
later:
Version File name Platform
---------------------------------------
7.00.702 S70702i.exe Intel
S70702a.exe Alpha
NOTE: Due to file dependencies, the most recent hotfix or feature that contains
the above files may also contain additional files.
WORKAROUND
To work around this problem, do either of the following:
Keep a single connection open when using DB-Library.
-or-
Use a different network library, such as named pipes or multiprotocol.
STATUS
Microsoft has confirmed this to be a problem in SQL Server version 7.0.
MORE INFORMATION
The memory leak is roughly 4 KB for each DB-Library connection opened to the
server.
This problem is specific to the use of the 32-bit DB-Library API, and the
problem only occurs when using the TCP/IP or IPX/SPX network libraries.
For an application that uses a single DB-Library connection, the memory leak
will hardly be noticeable. But for applications that either connect/disconnect
for each query ("make/break connections") or use multiple connections, the
problem can be more severe, causing all of the memory on the computer to be
consumed.
Additional query words: db lib dblib net netlib multi protocol
Keywords : SSrvDB_Lib kbbug7.00
Version : winnt:7.0
Platform : winnt
Issue type : kbbug
Herman verschooten <H.verschooten@WebVisie.net> on 02/11/2000 04:56:56 AM
Please respond to radiusnt@iea-software.com
To: "'radiusnt@iea-software.com'"
<radiusnt@iea-software.com>
cc: (bcc: David L Smith/Klein)
Subject: RE: [RadiusNT] RadiusNT and ODBC memory leak...
Dale,
I checked the versions thru the ODBC control panel applet, and found the
following:
SQL Server Driver : 3.70.06.90
ODBC Drivers all have: 3.510.3711.0
RadiusNT: 2.5.209
I reviewed previous mails about this subject and set the SQL-server memory
to fixed 150Mb, it first took about 20Mb (yesterday around 10am), but since
then it has already increased to 124.364k (mem usage) and 140504k (VM size)
on a machine with 256Mb. The only other thing that uses this SQL-server is
the authentication-dll for NTMail, which runs on another machine (SQL
3.60.0319, ODBC 3.510.3002.23) on the network.
Tx for any help,
Herman
-----Original Message-----
From: Dale E. Reed Jr. [mailto:daler@iea-software.com]
Sent: donderdag 10 februari 2000 18:42
To: radiusnt@iea-software.com
Subject: Re: [RadiusNT] RadiusNT and ODBC memory leak...
Herman verschooten wrote:
>
> Dale,
> we're experiencing the same problem, with SQL7 SP1, but the checkbox you
> mention is grayed out and checked. Do you know how to change this ?
Eith ODBC 3.x and higher, its up to the application to called the
SQLPrepare or SQLExecDirect, depending on whether the app wants the
quesy to be converted to a temp proc first. RadiusNT never calls
SQLPrepare, so this isn't an issue with the later ODBC Drivers.
What version of RadiusNT and ODBC drivers are you using? You'll
probably want to open a case with support if this is happening.
--Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart