Timeout settings determine how long the Jet Data Manager will wait for a process, before the delay in the process causes Jet to trigger an error. Timeout settings can be adjusted in several places depending on which database is being affected.
(Setting the timeout to 0 is tantamount to infinity.)
Types of Timeouts
The Connection Timeout is the length of time (in seconds) that the Jet Data Manager will wait for a connection to open. The default value is 15-seconds, but can be increased with slower network connections. The slower the connection, the higher this value will need to be.
(The connection timeout value is typically only relevant with external data sources.)
The Command Timeout is the length of time (in seconds) that the Jet Data Manager will wait for the command to execute. The default values are set differently depending on the type of database the Jet Data Manager is referencing. The Command Timeout may need to be increased on databases that have high data loads, such as the Staging database, where data cleansing equates to longer processing times.
(In error messages, the connection timeout setting is often referred to as the Execution Timeout. These errors are common, when Lookup Fields are used to lookup multiple values, such as when a Top function is used.)
Where to change the timeouts
You can change the timeouts in three places.
- Data source The standard settings are the same in all adapters with the exception of Microsoft Excel, text, and Any Source. (Any Source does not allow changes to these settings in some configurations.) The defaults are Connection 15 and Command 100. The Command Timeouts are low, because Jet only needs to transfer data from the source and no data cleansing is done here.
- Staging Database Here the default Command timeout is 1800 seconds, as a lot of data cleansing will be done in the staging database.
- Data Warehouse The Data Warehouse has settings similar to the staging database.