Is it slower to close and open a SQL Server connection instead of keeping it open?

Question

Hi! I'm developing an application with VB.NET which will be connecting to a SQL Server database, no other application will be connected to the database so I've got the following question: How will it be faster: closing and opening a connection when needed or keeping the connection open? I know that when many users connect the first option is better but since It will be only one user, which option is the best one?
Thanks and blessings since now!

Answer 1

Hi,



What is the latency between the app server and the database? If the two servers are connected together on the same 100Mbps or better switch, you'll do fine with the non-persistent connection. However, if your app server is in one data center and the other elsewhere consider using a persistent connection.



Regards

[e-mail]

Fully Managed Dedicated Servers and Virtual Machines - http://www.unixy.net

Answer 2

Opening connections to any database is one of the most expensive operations you do. It's part of the reason people started doing 'connection pooling'.



But if there is only one user, and that is how it will be forever, I don't see much point in keeping it open.



But if, in the future, this app will grow by users or traffic or volume, you'd want to plan for that. I've worked on apps that started in MSAccess for a team of 5, and ended up getting ported to Sql Svr for 100's!

Answer 3

at the start, there's a brilliant distinction between listening to and listening. you may hear extra smart in case you close up your eyes and eliminate any seen distractions. you pays attention extra smart if your eyes are open in view which you will discover expressions, tears, smiles and word physique language that may regularly say better than words do.