Skip to main content

Documentation Portal

Query timeouts

TrendMiner has 3 types of queries. For each of these types a separate timeout can be configured. These timeouts determine how long TrendMiner will wait for a response from the data source when querying it for data. Timeouts can be increased in case the data source or network towards the data source is underperforming.

Warning

Even though these timeouts can be configured, we recommend not increasing timeouts and looking for alternative solutions to increase the data source response times, as increasing timeouts might lead to degraded experience for end users.

Note that the appliance services also have query timeouts. Increasing timeouts on the connector does not guarantee a successful data call as other timeouts might be triggered instead.

Query timeouts can be configured in the connector configuration file.

Parameters:

<add key="query.interactive.timeout.secs" value="30"/> 
<add key="query.noninteractive.timeout.secs" value="90"/> 
<add key="query.batch.timeout.secs" value="300"/> 

Supported as of connector version: <3.4.485-b772a5d>

Supported for the following data source providers:

  • Aspentech IP21

  • TM connector

  • PI Data Archive (via PI AF SDK)

  • PI Data Archive (via PI AF SDK) – Active Directory Authentication

  • PI Data Archive (via OleDB)

  • PI Data Archive (via OleDB) – Active Directory Authentication

Parameters:

<add key="generic.query.interactive.timeout.secs" value="30"/> 
<add key="generic.query.noninteractive.timeout.secs" value="90"/> 

The generic properties default to "0", which means that the default timeouts of the respective drivers will remain in place.

Supported as of connector version: <3.4.485-b772a5d>

Supported for the following data source providers:

  • ODBC

  • OleDB

  • SQLite

In this section: