Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.the wait operation timed out.

Question

1.00/5 (2 votes)

See more:

I know if this error occures we need to set time out to be unlimited or 5min like that but. In my scenario when run this query in ssms window it takes only 1 sec to run but when i use ado.net it throw this error if someone faced it before please suggest the solution

What I have tried:

using (SqlCommand command = new SqlCommand(query, connection))
{


connection.Open();
command.CommandTimeout = 500;
    object result =command.ExecuteScalar();---error getting here

    model.StringID = result!=null? result.ToString():null;
    connection.Close();

    return model;
}

Posted 9-Oct-24 1:59am

Arul Kumar from Unknown

Add a Solution

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 · Answer 1 · 2024-10-09T02:30:00

We can't tell because we have no access to your command, or to your DB.

Start by using the debugger to establish exactly what query contains when your code executes, and copy that exact string into SSMS.

Then check that both bits of software are connected to the same database using the same database engine, on the same computers, using the same login information.

If you still get a disparity with all of that identical, add Stopwatch code to your using block to check the exact time each part takes - look for the actual bottle neck (which may be the Open, the ExecuteScalar, the ToString, or even the Close) before trying to work out where it's really slow.