I'm writing a VB.Net application that connects to a SQL 2000 database over the Web, For speed reasons it seems like it would be better to open the database connection when launching the program, and close the connection on exiting the program. So when making queries the database is always open. Would this cause a problem for SQL? Would there be any performance issues I should worry about?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Database Question
- Thread starter jward
- Start date
one of the main problems that i see with this (although i could be wrong) is that ADO.NET is made for a disconnected env. sounds like you want to keep the state open, and the current ver was just really not made for that. i would assume that connection pooling and everything comes into play. plus i'm really not sure how you are setting this up, client to web server, web server(farm) to app server, app server to databases.. ect. but you may run into some problems with you want to scale the system as well. but in the end it's up to you.
cheers.
--------------
cheers.
--------------
- Status
