D
dan
I'm trying to figure out the best practice for opening db
connections on an asp.net page. I have seen this done by
opening one connection for the page and using it for all
commands, and I have seen the connection open and closed
each time you run a command.
What is the best practice here? Is making the actual
connection each time slower than just keeping it open the
whole time, or is it better to free up database resources
in between commands?
connections on an asp.net page. I have seen this done by
opening one connection for the page and using it for all
commands, and I have seen the connection open and closed
each time you run a command.
What is the best practice here? Is making the actual
connection each time slower than just keeping it open the
whole time, or is it better to free up database resources
in between commands?