Is instantiating a .NET SQLConnection object on a per request basis (e.g. in the IOC container), for use with all the queries to be performed during that request typical?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is instantiating a .NET SQLConnection object on a per request basis (e.g. in the IOC container), for use with all the queries to be performed during that request typical?
Yes, this is reasonably common: because of connection pooling, an optimization technique that lets your program implicitly reuse connections to the database, this does not have as adverse an impact on performance as one might think.