Re: Timeout on my request!
- From: Chuck Norris <ciccone1978@xxxxxxxxx>
- Date: Thu, 06 Sep 2007 07:03:00 -0700
First, check the estimated execution plan of your query and, if it's
possible, try to optimize it.
If you have already done that,
why don't you schedule your query to run in background each night (or
each hour) and save the results in a DB table?
At this point in your web page do a simple 'select' statement to show
the data...surely it'll be faster.
:-)
On Sep 6, 3:40 pm, "Mark Rae [MVP]" <m...@xxxxxxxxxxxxxxxxx> wrote:
"Smith" <Sm...@xxxxxxxxxxxxxxxx> wrote in message
news:uStcNbI8HHA.5712@xxxxxxxxxxxxxxxxxxxxxxx
It all depends on the kind of data you work with. We are looking at
scientifc data here.
Data is data is data, at the end of the day...
Some of our queries can span over several hours.
In which case, I would be considering a different architecture, as the web
simply isn't designed for this kind of delay between Request and Response...
Have you thought about maybe some sort of messaging system where queries are
queued up waiting to be processed, and then the results emailed to the user
maybe as a PDF...?
--
Mark Rae
ASP.NET MVPhttp://www.markrae.net
.
- References:
- Timeout on my request!
- From: Smith
- Re: Timeout on my request!
- From: Mark Rae [MVP]
- Re: Timeout on my request!
- From: Smith
- Re: Timeout on my request!
- From: Mark Rae [MVP]
- Re: Timeout on my request!
- From: Smith
- Re: Timeout on my request!
- From: Mark Rae [MVP]
- Re: Timeout on my request!
- From: Smith
- Re: Timeout on my request!
- From: Mark Rae [MVP]
- Re: Timeout on my request!
- From: Smith
- Re: Timeout on my request!
- From: Mark Rae [MVP]
- Timeout on my request!
- Prev by Date: Re: Securing a single aspx page
- Next by Date: Session_Start/Session_End
- Previous by thread: Re: Timeout on my request!
- Next by thread: Re: Timeout on my request!
- Index(es):
Relevant Pages
|