Reusing Db connection

Agree! But needs some further explanation. When you persist objects, the Session is separate for every user, even for every browser window of the same user. So if you store the common connection in the Session you'll end up with a plenty of open connections. Otherwise, Application object is global for the whole application and allows you to keep a single object for all users. But using this to share connection can cause concurrency problems. It's used exactly the same way as Session. Cache is also global, like Application but provides some further enhancements like expiration policy.

It is not practical to keep the conection alive. If you have 40 users that will open browsers and make requesto to your page(and then page opens connection) and then close the browsers you will have 40 connections opened, that will cause DB troubles sometimes. But however you can put the connection in session, cache or application object. Example: Session["connection"] = conn; when using.. SQLconnection conn = (SqlConnectiion)Sesion["connection"];