13

I am gettting SQL time out error in my .net service.

As the service is already installed on the production, is there any way I can increase the timeout for the service from App.Config file.

At present, I am getting this exception after one minute, I have to make it to around 10 hours because the stored procedure we are using takes 2-2 hours to execute.

Improve this question
1
  • Actually those stored procedure needs to deal with many tables, I can't fight with the bussiness logic.. :-( Commented Oct 21, 2010 at 8:49

3 Answers 3

Reset to default
17

You could try setting the CommandTimeout property on your SqlCommand. I hope you are not doing this in an ASP.NET application.

Improve this answer
Sign up to request clarification or add additional context in comments.

2 Comments

Thanks for replying, Darin. But for that I need to deploy the service again. Is there any way I can make changes in App.Config file so I don't need to deploy that service again?
No, there is no way doing this in app.config.
1

You can set the timeout in your connection string with "connect Timeout = 100000000;" or whatever you want your timeout to be

Improve this answer

5 Comments

Can I put connection timeout in App.Config file?
No, you can't. This will have absolutely no effect. Command Timeout in connection string is ignored.
It works for me. You put it in your connection string, which is p in app.config or web.config if you set it up through a visual studio tool
Darin is right. Connect Timeout=1234 can be set in app.config. But that is just for connections. But the timeout for queries is controlled by command timeout which can not be set in app.config.
This is useless. The connect timeout is different than the command timeout. The connect timeout is only used to establish the connection, not to run queries.
1

The time out setting is up to database server.

In SQL Server Manager open the SQL Server Properties and pick the connection tab and set time out as big as You need.

Ps.

zero goes for no timeout.

Improve this answer

2 Comments

Thanks Vash. But I am getting .NET exception. If I am running the same stored procedure in SQL Server Managaement studio, it is allowing me to run that for the number of hours I want.
There is a timeout on the database server and there is a separate timeout on .net. Which ever is shorter is what will actually limit your run time.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.