Is there any problem in creating multiple database connections

Question

0.00/5 (No votes)

See more:

SQL-Server-2008

I have developed a .net windows TOP-UP application (HTTP LISTENERS) which accepts requests from Embeded devices

the application creates a thread along with unique database connection (SQL SERVER 2008 )for every request received from the devices and that connection rotates along the thread and the database connection closes when thread ends

i have observed that at peak hours number of requests received reaches to multiples of 100 also i have observed from the database by executing "SP_WHO" nearly 150-200 connection status is under "sleeping"

Is there any problem in creating these many database connections or any burden to the database

any other way to maintain these many requests at a time

Please Guide me......

Posted 19-Jun-14 19:44pm

sagar.panuganti

Add a Solution

Comments

Prasad Avunoori 20-Jun-14 1:49am

Why don't you kill the long sleeping process by running any sql job?

sagar.panuganti 20-Jun-14 1:54am

i have assigned 200 seconds in the connection string itself , Is there any problem with these SLEEPING connections.

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)

Raul Iloc · Accepted Answer · 2014-06-19T20:00:00

Solution 1

1.In generally the database connection are resources that should be used, then released as soon as possible, otherwise the speed and memory used by your database server will suffer.

2.So in your code open the connection only when is needed (access of the database data) and closed and release it as soon as possible (after the reading or updating of the data), and you should use try-catch-finally blocks for doing this!

Posted 19-Jun-14 20:00pm

Raul Iloc

Comments

sagar.panuganti 20-Jun-14 2:14am

as mentioned in the question opening a unique for a thread and i am accessing the database 5 times (select,insert,updates) and i will close the connection at the end of all these transactions ... so as u mentioned in the solution if i opened and closed the connections i have to open 5 times and close 5 times for every request... these many switching will create any problem...?