unclosed connections problem

We have recently migrated a classic asp/sql server web site from
windows server 2000 without the .net framework installed to windows
server 2003. We seem to be finding that sql server is using up
excessive amounts of RAM, much more than the old machine, even with
the same amount of traffic. I suspect there may be a number of
unclosed database connections in the legacy asp code and that windows
2003 is not shutting them down as quickly as with windows 2000. Does
this sound plausible and if so is their any temporary work around to
solve the problem. (It may take some time to correct all the code
problems)

Scott

William
Thu Nov 20 11:53:06 CST 2003

Is this ASP or ASP.NET?

I'd run a trace and see what's going on. You can control the maximum amount
of memory used but that's not probably what you are looking for.

I'd also make sure that all of my connections in code are being closed (I
know, not a very profound insight, but small mistakes are easy to make).
<scott_mcarthur2003@yahoo.co.uk> wrote in message
news:92c92d63.0311200931.34744d8a@posting.google.com...
> We have recently migrated a classic asp/sql server web site from
> windows server 2000 without the .net framework installed to windows
> server 2003. We seem to be finding that sql server is using up
> excessive amounts of RAM, much more than the old machine, even with
> the same amount of traffic. I suspect there may be a number of
> unclosed database connections in the legacy asp code and that windows
> 2003 is not shutting them down as quickly as with windows 2000. Does
> this sound plausible and if so is their any temporary work around to
> solve the problem. (It may take some time to correct all the code
> problems)
>
> Scott

William
Thu Nov 20 18:24:35 CST 2003

Turn on the Performance Monitor and watch the counters managed by the
SqlClient .NET Data Provider. These will show you the number of connection
pools as well as connections in the pool. If there is more than one pool per
application, your connection string is being changed each time the
connection is being opened. If your pool has more than a few connections,
then you're probably not closing connections correctly.

hth

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
MVP, hRD
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

<scott_mcarthur2003@yahoo.co.uk> wrote in message
news:92c92d63.0311200931.34744d8a@posting.google.com...
> We have recently migrated a classic asp/sql server web site from
> windows server 2000 without the .net framework installed to windows
> server 2003. We seem to be finding that sql server is using up
> excessive amounts of RAM, much more than the old machine, even with
> the same amount of traffic. I suspect there may be a number of
> unclosed database connections in the legacy asp code and that windows
> 2003 is not shutting them down as quickly as with windows 2000. Does
> this sound plausible and if so is their any temporary work around to
> solve the problem. (It may take some time to correct all the code
> problems)
>
> Scott

scott_mcarthur2003
Fri Nov 21 04:32:20 CST 2003

Thanks for the response, it is asp not asp.net. Do you have any idea
of which counters I should be running the trace on?

"William Ryan" <dotnetguru@comcast.nospam.net> wrote in message news:<ODTe664rDHA.2444@TK2MSFTNGP12.phx.gbl>...
> Is this ASP or ASP.NET?
>
> I'd run a trace and see what's going on. You can control the maximum amount
> of memory used but that's not probably what you are looking for.
>
> I'd also make sure that all of my connections in code are being closed (I
> know, not a very profound insight, but small mistakes are easy to make).
> <scott_mcarthur2003@yahoo.co.uk> wrote in message
> news:92c92d63.0311200931.34744d8a@posting.google.com...
> > We have recently migrated a classic asp/sql server web site from
> > windows server 2000 without the .net framework installed to windows
> > server 2003. We seem to be finding that sql server is using up
> > excessive amounts of RAM, much more than the old machine, even with
> > the same amount of traffic. I suspect there may be a number of
> > unclosed database connections in the legacy asp code and that windows
> > 2003 is not shutting them down as quickly as with windows 2000. Does
> > this sound plausible and if so is their any temporary work around to
> > solve the problem. (It may take some time to correct all the code
> > problems)
> >
> > Scott

William
Fri Nov 21 10:47:52 CST 2003

In that case (sigh) the only counters you can draw on are those exposed by
SQL Server itself. There's a set in "General Statistics" (?) IIRC that shows
user connections. I would REALLY consider migrating that application to
ASP.NET... it's a vastly improved platform.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
MVP, hRD
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________

<scott_mcarthur2003@yahoo.co.uk> wrote in message
news:92c92d63.0311210232.18808986@posting.google.com...
> Thanks for the response, it is asp not asp.net. Do you have any idea
> of which counters I should be running the trace on?
>
> "William Ryan" <dotnetguru@comcast.nospam.net> wrote in message
news:<ODTe664rDHA.2444@TK2MSFTNGP12.phx.gbl>...
> > Is this ASP or ASP.NET?
> >
> > I'd run a trace and see what's going on. You can control the maximum
amount
> > of memory used but that's not probably what you are looking for.
> >
> > I'd also make sure that all of my connections in code are being closed
(I
> > know, not a very profound insight, but small mistakes are easy to make).
> > <scott_mcarthur2003@yahoo.co.uk> wrote in message
> > news:92c92d63.0311200931.34744d8a@posting.google.com...
> > > We have recently migrated a classic asp/sql server web site from
> > > windows server 2000 without the .net framework installed to windows
> > > server 2003. We seem to be finding that sql server is using up
> > > excessive amounts of RAM, much more than the old machine, even with
> > > the same amount of traffic. I suspect there may be a number of
> > > unclosed database connections in the legacy asp code and that windows
> > > 2003 is not shutting them down as quickly as with windows 2000. Does
> > > this sound plausible and if so is their any temporary work around to
> > > solve the problem. (It may take some time to correct all the code
> > > problems)
> > >
> > > Scott

scott_mcarthur2003
Sat Nov 22 18:55:13 CST 2003

"William \(Bill\) Vaughn" <billvaRemoveThis@nwlink.com> wrote in message news:<OOlzP6EsDHA.2828@tk2msftngp13.phx.gbl>...
> In that case (sigh) the only counters you can draw on are those exposed by
> SQL Server itself. There's a set in "General Statistics" (?) IIRC that shows
> user connections. I would REALLY consider migrating that application to
> ASP.NET... it's a vastly improved platform.
>

I have checked this and it seems as if there are relatively few
connetions which don't seem to be growing much. I guess this points in
the direction of a memory leak of some sort, any ideas on how to
diagnose?

Your reply is much appreciated.

Scott