Can I avoid closing a SqlConnection with a local db?

Question

0.00/5 (No votes)

See more:

Hi,

I'm writing an application which uses a connection to a mdf sql db.
I use this using a SqlConnection object.
Since the db is a local one which no-one can access but me, can I keep the connection opened from the application starting to the ending?

Thanks a lot!

Jymmy097

Posted 9-May-14 10:06am

LLLLGGGG

Add a Solution

Comments

[no name] 9-May-14 16:09pm

Sure you could. It's not a good idea to get into developing bad habits but you can do whatever you want.

LLLLGGGG 9-May-14 16:14pm

I know that's a bad habit, but I don't want to close the connection and reopen it.are there performance issues opening and closing a connection? Because I fear there are... That's why I didn't want to close it.
Is it a good argument as I'm a newbie in this field?

[no name] 9-May-14 16:28pm

No it is not a good argument :-) You are more likely to notice a "performance issue" from your queries, not from opening and closing the connection. Opening and closing the connection is probably the least of your worries.

LLLLGGGG 9-May-14 16:49pm

Ok, thanks a lot!! Sorry for the stupid question, but It's only some day since I've started to learn Sql and Connections.

[no name] 9-May-14 16:52pm

Not a problem at all. As a side note, opening the connection has been optimized for performance using a connection pool. Read more about it, http://msdn.microsoft.com/en-us/library/8xx3tyca(v=vs.110).aspx

Codefroster 9-May-14 17:04pm

Nice answer wes aday agreed with you

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2014-05-09T10:45:00

You can, as Wes has said. But... It isn't a good idea.
If you are using it locally only, then probably you shouldn't be using it via SQL - ACE/ODBC is probably a better idea, because it means that you have to change the code in order to convert it to a multiuser system. Using SQL for single user and coding for a single user is dangerous, because in 3 months time you will have forgotten that when you release the software to a dozen other users and sit back in pride watching the whole system fall over from time to time... :laugh:

It's poor practice for a reason: because they can cause problems later on when it's a lot, lot more expensive to find and fix them.