how to avoid [System.Data.SqlClient.SqlException] = {"Timeout expired. "}

Question

0.00/5 (No votes)

See more:

SQL-Server-2005

how to avoid [System.Data.SqlClient.SqlException] = {"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not "}
when i will be update the SQL query update join query at time 1000 records in the database at every second. it will be shown this exception.
any one have idea about this exception
thanks in advance.

Posted 20-Jun-11 4:16am

vrushali katkade

Add a Solution

3 solutions

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)

Kim Togo · Answer 1 · 2011-06-20T04:26:00

Solution 1

You can change SqlCommand.CommandTimeout[^] to are lager value then the default at 30 sec.

Posted 20-Jun-11 4:26am

Kim Togo

Comments

thatraja 20-Jun-11 10:40am

You beat me to it man, 5!

Kim Togo 20-Jun-11 10:41am

Thanks

vrushali katkade 20-Jun-11 23:58pm

i have already set SQLcommand.timeout=120

Kim Togo 21-Jun-11 2:19am

Then perhaps the problem is else were. Please see Solution 3 from Dylan Morley.

thatraja · Answer 2 · 2011-06-20T04:40:00

Increase value for Timeout of your SQL Connection & SQL Command

For Connection in Web.Config,

<add key="ConnectionString" value="server=(local); uid=sa; password=sa; database=master;Connection Timeout=30" />

For Command,

public void CreateSqlCommand()
{
   SqlCommand cmd = new SqlCommand();
   cmd.CommandTimeout = 15;
   cmd.CommandType = CommandType.Text;
}

& also take a look at the following page.
Troubleshooting: Timeout expired[^]

Free attachment
DBA’s Quick Guide to Timeouts[^]

Dylan Morley · Answer 3 · 2011-06-20T05:37:00

Increasing the command timeout will solve the problem, but you are addressing the issue rather than the cause

Default query timeout is 30 seconds, so assuming you haven't changed this your queries are taking 30 seconds to run and then reporting timeout.

Can you tune your queries at all?

* Are all tables included in the query correctly indexed. Clustered index on tables etc?
* Have you run your query through Execution Planner? Any areas that could be improved?
* Is only the data you need to update being updated?

You should definitely have a look at the source of the problem first and see if you can improve things here.