Connection TimeOut Expires in ASP.Net

Question

0.00/5 (No votes)

See more:

, +

I have an aspx page that throws an exception of ODBC Connection Timeout expires while executing an Remote SQL SERVER Stored Procedure having large volume of data.How to Solve this problem.
Please Help.

Posted 7-Sep-11 1:52am

Deepak.xip

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)

uspatel · Answer 1 · 2011-09-07T02:08:00

Solution 2

change in web config file as
set maxRequestLength as Your request.
in this example max size is 60 mb .

HTML

<httpruntime executiontimeout="110" maxrequestlength="60000" />

Posted 7-Sep-11 2:08am

uspatel

MaulikDusara · Answer 2 · 2011-09-07T03:15:00

Solution 3

hi Deepak.xip,

Follow this:

1) Create index[^] in your database.

2) Paging using PagedDataSource class[^]

) try to Optimize SQL queries 1[^] Optimize SQL queries 2[^]

Posted 7-Sep-11 3:15am

MaulikDusara

#realJSOP · Answer 3 · 2011-09-07T02:08:00

You could try one of these:

0) Retrieve data in smaller chunks

1) Try changing the CommandTimeout property in the SqlCommand object to a higher value (the default is 30 seconds).

2) Use the asynchronous functionality in SqlCommand (BeginExecuteReader).

EDIT ===================

Why was this answer voted 1? I provided several viable strategies. If you were expecting code, you're going to be sorely disappointed because nobody here is going to be able to provide it to you. Why? because we're not familiar with your project, and nobody here works for free.