Looking for the previous version? View v2024.06 documentation →
Connection Profiles — Query Timeout
Set a maximum query execution time on a connection profile to prevent runaway queries from consuming database resources.
Overview
The Query Timeout In Seconds setting on a connection profile caps the maximum time Data Trust will wait for a single query to complete against that data source. Any query that exceeds the timeout threshold is automatically terminated, preventing long-running or runaway queries from consuming database resources indefinitely.
Prerequisites
- You are logged in to Data Trust with an Admin Pro-User role.
- The connection profile you want to configure already exists in the Connection Explorer.
Setting the Query Timeout
Path: Data Trust › Admin Console › Connection Explorer › Edit Connection › Additional Settings- Navigate to Admin Console › Connection Explorer.
Figure 1: Connection Explorer — the main listing page showing all connection profiles.
The Connection Explorer lists every profile in the system with status, source type, and ownership details. Locate the connection you want to configure and select its checkbox to activate the toolbar actions.
- Select the checkbox next to the target connection (e.g., MSSQL_JDBC) and click the Edit icon, or click the connection name directly.
Figure 2: Select the target connection and click the Edit icon (or the connection name) to open the Edit Connection page.
Checking the row highlights it and activates the toolbar action icons. Alternatively, clicking the blue connection name link directly opens the Edit Connection page without needing to use the toolbar.
- The Edit Connection page opens showing the current Connection Parameters tab.
- Click the Additional Settings tab.
Figure 3: Edit Connection page — click the “Additional Settings” tab to access the timeout configuration.
The Edit Connection page displays the current connection details. The left panel shows the connection name, source name, and connection type (read-only). The right panel has two tabs: Connection Parameters (credentials and connection string) and Additional Settings (performance and access controls). Click Additional Settings to proceed.
Figure 4: Additional Settings tab showing the Query Timeout In Seconds field (currently empty — no timeout applied).
The Additional Settings tab shows performance parameters: Default Parallelism, Max Parallelism, Default and Max Packet Size, User Groups, and the Query Timeout In Seconds field at the bottom. An empty Query Timeout means queries on this connection have no time limit.
Figure 5: All Additional Settings fields — Default Parallelism (1), Max Parallelism (20), packet sizes, and an assigned User Group are shown alongside the empty Query Timeout field.
This view shows a fully configured Additional Settings tab. The User Groups field shows the groups that have access to this connection (e.g., Alekhya’s Group). The Query Timeout In Seconds field at the bottom is the one you need to set.
- Click into the Query Timeout In Seconds field and enter the desired timeout value in seconds (e.g.,
1for testing,300for five minutes in production).
Figure 6: Query Timeout In Seconds field with a value set — this caps query execution time to the specified number of seconds.
Enter a positive integer representing the maximum number of seconds allowed for any single query. The field has up/down spinner arrows for incremental adjustment. A value of 300 means any query taking longer than 5 minutes will be automatically terminated. Leave blank (or set to 0) to allow unlimited query duration.
- Click Save to apply the timeout setting.
A green “Values saved successfully” toast notification confirms the setting is stored.
Figure 7: Green “Values saved successfully” toast confirming the Query Timeout value has been persisted.
The toast appears in the top-right corner of the Edit Connection page. The timeout is now active for all queries using this connection. The Query Timeout field returns to blank in the display — this is normal; the value is saved in the background.
Observing the Timeout in Query Studio
Once a query timeout is configured, it takes effect the next time a query is run against this connection from any Data Trust module (Query Studio, Scenario Builder, Batch Console, etc.).
Figure 8: Query Studio — the connection selector shows the MSSQL_JDBC connection that now has a query timeout configured.
In Query Studio (or Query Generator), the Connection dropdown at the top lists all available connection profiles. Selecting the connection that has a timeout configured means any custom SQL query you run against it will be subject to that timeout.
Figure 9: A custom SQL query in Query Studio — when executed against a connection with a timeout, any query exceeding the configured limit will be terminated automatically.
When a query runs longer than the configured Query Timeout In Seconds value, Data Trust automatically cancels the query and returns a timeout error to the user. This protects the database from resource exhaustion caused by poorly written or unexpectedly large queries.