There's an application
which runs on .NET Framework 1.1 and uses SqlClient class to connect to
database.
It is a server application, but sometime the application is closed without
letting int finish it's job.
I've seen that when this happens there could be open connections to the
database.-
Is there a way, in which I can check if there are unused connections and
destroy them the next time I open the application?.

When an application is closed the connections it "owns" are closed and
disposed automatically.
In IIS, your application is hosted by a proxy that holds ownership. When
your "application domain" ends, the connections it owns are closed and
destroyed.

--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
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.
__________________________________

"Eduardo Fonseca B." <(E-Mail Removed)> wrote in
message news:A1DFDDF0-99E5-48FF-9195-(E-Mail Removed)...
> There's an application
> which runs on .NET Framework 1.1 and uses SqlClient class to connect to
> database.
> It is a server application, but sometime the application is closed without
> letting int finish it's job.
> I've seen that when this happens there could be open connections to the
> database.-
> Is there a way, in which I can check if there are unused connections and
> destroy them the next time I open the application?.