unclosed connections problem

[scott_mcarthur2003@yahoo.co.uk]

We have just migrated from a windows 2000 server running classic
asp/sql server web sites without the .net framework installed to
windows 2003. Despite having the same traffic levels sql server on the
new machine seems to be using up much more RAM than before. I suspect
that their may be unclosed database connections in the asp code and
that the reason is that windows 2003 is not shutting down unused
connections as quickly. Is this feasible? If so is their any
workaround as it might take some time to fix all the connections in
the code.

[Aaron Bertrand - MVP]

It could be a variety of other things, for example your 2003 installation
might just have a smaller memory footprint than your 2000 server, and so
more RAM is available for SQL Server to use. It could also be that you have
a different min/max memory level configured for SQL Server on the new
machine.

Unless it is actually disruptive (e.g. other programs can't get enough
memory to run), you should not be alarmed about the amount of RAM SQL Server
is using.

--
Aaron Bertrand
SQL Server MVP
[url]http://www.aspfaq.com/[/url]




<scott_mcarthur2003@yahoo.co.uk> wrote in message
news:92c92d63.0311200950.15e82873@posting.google.c om...

> We have just migrated from a windows 2000 server running classic
> asp/sql server web sites without the .net framework installed to
> windows 2003. Despite having the same traffic levels sql server on the
> new machine seems to be using up much more RAM than before. I suspect
> that their may be unclosed database connections in the asp code and
> that the reason is that windows 2003 is not shutting down unused
> connections as quickly. Is this feasible? If so is their any
> workaround as it might take some time to fix all the connections in
> the code.