Huge Data update results in script time out - ASP page

[porchelvi]

Hi everyone,

I have a problem with huge data update (like 4000 lines of text ) in the Database through ASP page. IE error was : Script timed out. I believe that the Application process runs out of memory as there are like 115 ASP application on the IIS. I have noticed that the page gets updated in 1.5 min in local IIS where as the server takes 5 min to display error. What can i do best at this situation? Can anybody tell me where can i see ASP process running and explain abt it.


Thanks in Advance

[nedu]

Hi,

You shall set the Scripttimeout using following syntax

Server.ScriptTimeout[=NumSeconds]


Try This . .

Regards,
Nedu. M

[porchelvi]

Hi,

You shall set the Scripttimeout using following syntax

Server.ScriptTimeout[=NumSeconds]


Try This . .

Regards,
Nedu. M

Hi Nedu,


I tried increating the script timeout seconds.. nothing works.. what can i do?

[nedu]

Hi,

Try this

http://support.microsoft.com/kb/268364

Regards,
Nedu. M

[porchelvi]

Hi,

Try this

http://support.microsoft.com/kb/268364

Regards,
Nedu. M

I tried all that. Nothing works.. the upate action is eating up 100 % of CPU usage and 63% of the available memory. i think the problm is with the ASP process memory.

thanks
Porchelvi

[nedu]

Hi,

I think u r updating the DB. Try using the SP for updation.


Regards,
Nedu. M

[CroCrew]

Hello porchelvi,
Can you post the complete code of the page that you are using to update your database? Please mask out your connection string but, let us know the type of database that you are using. Maybe we can optimize the page for you and get everything working.

CroCrew~

[markrawlingson]

BOOO.

Script timeouts should be stricken from all programming languages.

If the standard script timeout is maxing, that indicates a problem with the efficiency in your code. If you put 500lbs of weight on a camel's back, it will lay down - even if it the strongest camel in the world, there's always a breaking point.

Fix the problem at its core, don't create a bandaid solution, it only causes more problems in the future.

As CroCrew said, show the code and perhaps we can offer up some optomizations for you within the script. This will speed up the script by making the actual code more efficient.

Sincerely,
Mark