Time out issue in classic ASP

Question

0.00/5 (No votes)

See more:

Hi All,

I am working on a classic ASP project where I am getting time out issue when populating the data from DB and Bind it in the UI.

To resolve the issue we tried to do the pagination but it went un successfull.

Can any one suggest me, whether we have any other approaches to fix the issue.

Regards
Prashant P

Posted 18-May-14 23:08pm

Prashant Bangaluru

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)

Keith Barrow · Answer 1 · 2014-05-19T01:52:00

Without code it is hard to say what is happening. With databases, it could be a lot of things.

First I'd suggest you need to optimise how your pagination is happening - if you paginate your get fewer rows so the performance should shoot up - something is wrong here, you need to examine the join orders of the tables involved. Overall this can be a fairly complicated process. Secondly, your data schema might be inefficient. You might need to add indexes to columns that are used for joins, assuming they aren't primary or foreign keys already. Finally, if you are not running your SQL as a stored procedure, migrate it across - though this is unlikely to help if your SQL is running this slowly.