connection timeout error

Question

4.00/5 (1 vote)

See more:

SQL-Server-2012

we are getting connection time out in our application for 2-3times intially when we use,after this the application is working fine for whole day.this is getting repeated for everyday.

application is hitting our test db server,no of users are also very less

my observations

->i can't see any time out error in log

->no blockings and deadlocks

->remote login timeouts &remote query timeout run value are set to 1000

->in application connection time out is set to zero and command time out set to 240,i have tried both with zero but it didn't worked

->cpu and memory utilization are also normal

server is on SQL 2012

could some one help me on this to overcome the initial time out error in application and the things which need to be modified or monitored from DB end

Posted 7-Oct-14 1:25am

Member 11135033

Add a Solution

Comments

renish patel 7-Oct-14 7:33am

You used database from Network? If yes,then check your network connectivity.

PhilLenoir 7-Oct-14 8:59am

Have you tried looking at your network itself? Could you have a noisy card or port? Are any other network accesses occasionally slow? CPU/memory on both client and server?

You could try a packet sniffer (on both client and server).

jkirkerx 7-Oct-14 16:15pm

Did you look at the event log on the sql server, and check for SQL messages?

Member 11135033 7-Oct-14 23:59pm

network connectivity is fine,i couldn't find any error message in logs aswell

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)

jkirkerx · Answer 1 · 2014-10-07T10:26:00

That's like finding a needle in the haystack because you are not able to get a general idea of where to look.

1. So look at your event logs in the database server first.
2. Check your code, do you open the database just in time, and then close it.
3. Check your application design, or poorly written SQL, streamline functions to access the server less.
4. Sometimes you have to change the settings on the Microsoft SQL Server to sort of create an open connection for a longer period of time.

Consider this
http://stackoverflow.com/questions/312702/is-it-safe-to-keep-database-connections-open-for-long-time[^]

I can say that when you figure it out, that may never happen again on your watch.

FYI:
I had a similar error last week, but it was due to the Veeam Backup Software that brought the server offline for a minute to do a full backup.