Hi All,

In sql server, the number of connections increases exponentionally and they are not closed. In my asp.net page i even added statement to close the connection in Finally block of exception handling.

I am facing a serious issue due to this.

Can any one please help on this...

regards
dsekar_nat

__________________
Regards,
dsekar_nat

You only have to open ONE connection at the top of the page and close it at bottom of page. You can call the database many times between without having to close and reopen connection. If you do this, your design has to be changed.

Only problem with Peso comments is what happens if the client disconnects while executing the page? Does the open connection section of the code get orphaned and never get to the close connection part? Ideally you should do it the way PHP does, I am not sure how to do this with asp though. The apache/php code opens a connection to the sql server and keeps it open for the execution of multiple pages with multiple clients. Constantly opening and closing sql connections causes wasted overhead on both your SQL server and your web server. As well each open connection consumes memory on your SQL server. This question may be better posted in an ASP forum.