"Aaron Bertrand - MVP" wrote:
However, increasing a timeout value is like bandaging a broken
bone...
...as I stated above, if your ASP page takes longer than 90
seconds to return a result, your problem is much deeper than
a simple timeout setting.
This is either arrogant or ignorant, Aaron. Even your own article
acknowledges that some script runtimes are beyond the developer's control.
I have a script that uploads (into SQL Server) the contents of a vendor's
proprietary database, the completion of which requires a vendor-supplied
interface. My script takes 15-20 minutes to run (for a mere 15,000 records),
so I crank up the ScriptTimeout.
My script has been functioning flawlessly for two years, and the vendor
finally offered a tool to extract their DB into Access (but no other DB).
Turns out my script is just as fast as the vendor's own tool, so we left it
alone.
Some may question the use of a web script for this, but I find that it
offers many benefits, especially security and the ability to run the job on
demand from anywhere on the network.
On the down side, we had to install the vendor's API on one of our web
servers.
--
Dave Anderson
Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.