Best Practice? 1

[MadJock]

Folks,

I have written an ASP page that connects to SQL Server. I have two versions of the page and am unsure which one is best practice. There can be a significant pause between each part of the execution.

Version 1

open connection
perform query
perform query
perform several queries
write record
close connection

Version 2

open connection
perform query
close connection
open connection
perform query
close connection
open connection
perform several queries
close connection
open connection
write record
close connection


Any advice appreciated as always,

Graeme

website:

http://www.graeme-taylor.co.uk

 

[gsc1ugs]

I'm not sure what first one is doing but there is no need to keep closing a connection until you've finished with the database

gsc1ugs gsc1ugs
"Cant see wood for tree's...!"

 

[gsc1ugs]

As long as you update after each query

gsc1ugs gsc1ugs
"Cant see wood for tree's...!"

 

[MadJock]

My basic question is - what is creates a lighter load on the server -

a) One lengthy connection with light use
b) Lots of short connections

My application in theory could be accessed by hundreds of users.

Thanks,

Graeme
website:

http://www.graeme-taylor.co.uk

 

[cbokowski]

I would suggest taking a look at using get rows for your querys. We have seen huge (10 times faster) increases in performance.


check out these links for great info.....

http://www.learnasp.com/learn/whygetrows.asp

and

http://www.learnasp.com/learn/getrowsultimate.asp