ADO.NET Connections and Connection Pools
-
Just started to read up on ADO.NET. Do I understand this correctly: Normally, when I code a C++ app I open a connection or two when I first start my app. I keep the connection open until my app is closed. I would created and destroy command objects many times during the life of the app. With ADO.NET am I supposed to call Close on the Connection after EVERY time I get done using it? - - Because there is a connection pool that it is returned too.
-
Just started to read up on ADO.NET. Do I understand this correctly: Normally, when I code a C++ app I open a connection or two when I first start my app. I keep the connection open until my app is closed. I would created and destroy command objects many times during the life of the app. With ADO.NET am I supposed to call Close on the Connection after EVERY time I get done using it? - - Because there is a connection pool that it is returned too.
Yep, that is pretty much it. I think the connection pooling is more for ASP.NET but also think that when you are holding on to a connection, that is one more connection license being used on the server. If you happen to run against MSDE, there are only five I believe before it throttles down. You have to use planning though, as there is an time overhead in establishing those connections depending on where the server is located. Rocky Moore <><