better approaches

[Vicky]

which one is better approach among the two listed below

1. Opening connection on each web page for doing some database transaction

2. Opening connection once and store it in application object, and then
refering this application object on each web page.

Thanks

[.NET Follower]

dear vicky
both r wrong
store ur connectn string always in the web.config files
as
<appSettings>

<add key="anyname" value="Data source=xyz;initial catalog=DBNAME;user
ed=sa;password=sa"/>

<add key="TimeOut" value="10"/>

</appSettings>
--
Thanks and Regards,

Amit Agarwal
Software Programmer(.NET)
"Vicky" <vi*********@rediffmail.com> wrote in message
news:%2******************@TK2MSFTNGP09.phx.gbl...

which one is better approach among the two listed below

1. Opening connection on each web page for doing some database transaction

2. Opening connection once and store it in application object, and then
refering this application object on each web page.

Thanks

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.574 / Virus Database: 364 - Release Date: 1/29/2004

[Vicky]

I think u misinterpreted by question, i mean not connection string but
instance of open connection object connected to a Sql server database

thanks
".NET Follower" <am*************@SoftHome.net> wrote in message
news:uI**************@tk2msftngp13.phx.gbl...

dear vicky
both r wrong
store ur connectn string always in the web.config files
as
<appSettings>

<add key="anyname" value="Data source=xyz;initial catalog=DBNAME;user
ed=sa;password=sa"/>

<add key="TimeOut" value="10"/>

</appSettings>
--
Thanks and Regards,

Amit Agarwal
Software Programmer(.NET)
"Vicky" <vi*********@rediffmail.com> wrote in message
news:%2******************@TK2MSFTNGP09.phx.gbl...

which one is better approach among the two listed below

1. Opening connection on each web page for doing some database transaction
2. Opening connection once and store it in application object, and then
refering this application object on each web page.

Thanks

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.574 / Virus Database: 364 - Release Date: 1/29/2004

[Munsifali Rashid]

I think generally, it's better to open the connection, do your database
stuff, and then close the connection on each page. As far as I know, the
connnection pooling and optimisation stuff is done by the .net framework and
windows.

Mun
--
Munsifali Rashid
http://www.munsplace.com/


"Vicky" <vi*********@rediffmail.com> wrote in message
news:Oj****************@tk2msftngp13.phx.gbl...

I think u misinterpreted by question, i mean not connection string but
instance of open connection object connected to a Sql server database

thanks

[Rocky Moore]

Option (3) ;)

You should use a connection and then close it when you no longer need it. If
you have a group of calls you want to make, you can open the connection and
live it open until the rest of the steps are complete (as long as there is
no collision on the connection), but it is best if this time frame is short,
you would not want to leave connections open past the duration of the page
request. In this way you allow the ADO.NET handling of connection pooling
to function.

If you are using datasets, simply allow the adapter to open and close the
connections as required.

As a side note, make sure you close all your datareaders when you are
finished with them (if you use them at all).

--
Rocky Moore
www.HintsAndTips.com - Share your tips with the world!
~~~~~~~~~ Developer Tips Welcome! ~~~~~~~~~

"Vicky" <vi*********@rediffmail.com> wrote in message
news:#M**************@TK2MSFTNGP09.phx.gbl...

which one is better approach among the two listed below

1. Opening connection on each web page for doing some database transaction

2. Opening connection once and store it in application object, and then
refering this application object on each web page.

Thanks

[.NET Follower]

ya
i misinterprated ur ?

it is always a better practise to open and close ur DB connectn
immediately on every page.
imagine numerous clients opening a connection to DB
so how much resources is blocked
and so ur app will definately crash.

some objects like the dataadapter does itself this job

however for Action queries like ExecuteNONQuery etc
u hv to xplicitly open and close connectn s

so 1 is recommended.

--
Thanks and Regards,

Amit Agarwal
Software Programmer(.NET)
".NET Follower" <am*************@SoftHome.net> wrote in message
news:uI****************@tk2msftngp13.phx.gbl...

dear vicky
both r wrong
store ur connectn string always in the web.config files
as
<appSettings>

<add key="anyname" value="Data source=xyz;initial catalog=DBNAME;user
ed=sa;password=sa"/>

<add key="TimeOut" value="10"/>

</appSettings>
--
Thanks and Regards,

Amit Agarwal
Software Programmer(.NET)
"Vicky" <vi*********@rediffmail.com> wrote in message
news:%2******************@TK2MSFTNGP09.phx.gbl...

which one is better approach among the two listed below

1. Opening connection on each web page for doing some database transaction
2. Opening connection once and store it in application object, and then
refering this application object on each web page.

Thanks

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.574 / Virus Database: 364 - Release Date: 1/29/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.574 / Virus Database: 364 - Release Date: 1/29/2004

[Vicky]

Thanks, i too was doing this only.

"Munsifali Rashid" <mun.news@#RemoveToReply#cordlessmouse.co.uk> wrote in
message news:uV**************@TK2MSFTNGP10.phx.gbl...

I think generally, it's better to open the connection, do your database
stuff, and then close the connection on each page. As far as I know, the
connnection pooling and optimisation stuff is done by the .net framework and windows.

Mun
--
Munsifali Rashid
http://www.munsplace.com/


"Vicky" <vi*********@rediffmail.com> wrote in message
news:Oj****************@tk2msftngp13.phx.gbl...

I think u misinterpreted by question, i mean not connection string but
instance of open connection object connected to a Sql server database

thanks