Re: SqlConnection Object in Application Variable OR Session Variable OR open/close
- From: "Marina Levit [MVP]" <someone@xxxxxxxxxx>
- Date: Thu, 31 Aug 2006 12:50:16 -0400
1. This is the most horrible method. All users would share the same
connection object, which means, you are going to have multiple threads
trying to use it at once, which means your app will crash instance under any
kind of load.
2. This is slightly better, but still really bad. First off, it means you
have an open connection the entire lifetime of a session. This severely
limits the number of concurrent users, and performs badly.
3. This is how you should handle it. Connections are pooled by default,
opening and closing them is relatively inexpensive. Additionally, you will
get much better performance by not keeping unecessary connections open, 99%
of which time they are not being used.
So yes, #3 is the way to go.
"pratham" <praveen.config@xxxxxxxxx> wrote in message
news:1157042602.098674.82410@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi and regards
What is best method to have an connection to sql, iam using sqlserver
1. have an sqlconnection open when the application start event in
global.asax so that i dont have to open it in each method where i
require to open an connection
2. open an connection in seesion so that, it is available in session of
the user thorugh out
3. open an connection in each method and close after the requried
operation is completed
which is better
as per the 3rd method ... doest openning and closing in each method is
a bad??
Comments expected
.
- Follow-Ups:
- References:
- Prev by Date: SqlConnection Object in Application Variable OR Session Variable OR open/close
- Next by Date: Re: Using Access Database on Different Location for .NET 2.0
- Previous by thread: SqlConnection Object in Application Variable OR Session Variable OR open/close
- Next by thread: Re: SqlConnection Object in Application Variable OR Session Variable OR open/close
- Index(es):
Relevant Pages
|
