in reply to Memory Issues with DBI proxy on Windows

It is entirely normal for SQL server to allocate memory to each session that logs on and it has nothing to do with perl. So as stated I don't see the problem. Or are you saying that sessions are staying alive after the linux client has disconnected? Is the memory larger than the amount suggested by the SQL being performed? How did you decide that this was the case?

For further information about administering and configuring SQL Server installations, you might want to look somewhere like this: http://www.informit.com/guides/guide.asp?g=sqlserver

One world, one people

  • Comment on Re: Memory Issues with DBI proxy on Windows

Replies are listed 'Best First'.
Re^2: Memory Issues with DBI proxy on Windows
by dwcumper (Initiate) on Jul 15, 2005 at 17:42 UTC
    The problem isn't with SQL server itself. That's actually on a different server. The problem I'm having is with the DBI proxy process that is located on a server by itself.
    After each connection the size of the memory taken by the perl process grows by about 3-4 megs and the memory is never given back to the OS after the linux client disconnects from the proxy. So after running for awhile, the perl process ends up taking up 150 megs or more of memory and then stops responding. At that point the process has to be killed and restarted to free the memory and get the process working again.
[reply]

In Section Seekers of Perl Wisdom