This question came into me via an email and hallway conversation regarding very long running queries.
Situation:
User may not have appropriate permissions to access to the full set of tables that might be required for running the query in a previously saved .jmpquery file.
Problem:
User may have to wait an unusually longtime for the query to fail or return no results because of the default timeout settings.
Solution:
There are a couple of options for modifying the timeout ( how long, in seconds, a remote operation can take before the Server times out) that can be added to the ODBC driver during or after configuration.
Option 1—
On the ODBC driver configuration there should be an option to specify the database name:
For example, if the database name is JMPDB then you could specify in the field the following:
JMPDB?queryTimeout=25
Modifying query timeout with a Windows PostgreSQL ODBC driverModifying query timeout with a Windows PostgreSQL ODBC driver Option 2—
In the Connect Setting box add the following:
(In the PostgreSQL driver configuration this was found on page 2 of the settings)
set query Timeout to 25
Connection Settings using Windows PostgreSQL ODBC driverConnection Settings using Windows PostgreSQL ODBC driver
Please note that only one of the options can be used.
And if a timeout of 0 is specified as the query timeout the driver will continue to wait indefinitely or until the query finishes.
Cheers,
Stan
