30-Second Timeout

If you use Microsoft Access data access pages, you might encounter problems with a 30-second default timeout if your queries run slow. Here's a tip for avoiding the problem.

Mark Solomon

January 21, 2003

1 Min Read
ITPro Today logo

If you're following the techniques described in the main article, you might want to simplify the process of connecting to the System Monitor—generated tables by using Microsoft Access data access pages to query the tables directly. However, you'll probably find that queries you create access unindexed data, making them run especially slow. Additionally, data access pages seem to have a bug; they won't accept the Connect Timeout property and instead use a default timeout of 30 seconds. So if you use data access pages to view System Monitor—logged data, you need to perform some data transformation to avoid the 30-second limitation. We suggest you create an alternate data repository in SQL Server in which you can store and manipulate the System Monitor data to suit your needs—and avoid the 30-second limitation.

Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like