Editor Connection Idle Timeout

Configure automatic release of editor connections after a period of inactivity to prevent unexpected billing on serverless databases.

DBCode maintains dedicated connections for SQL editor tabs to support features like transaction control. These connections run periodic keepalive queries to prevent server-side disconnection.

For serverless or pay-per-query databases like Redshift Serverless, Snowflake, BigQuery, and Databricks, these keepalive queries can result in unexpected charges. The Editor Connection Idle Timeout setting allows you to automatically release these connections after a period of inactivity.

Configuring the Idle Timeout

The idle timeout is configured per-connection in the Advanced section of the connection settings:

  1. Open the connection configuration (click the edit icon on your connection)
  2. Scroll to the Advanced section
  3. Set Editor Connection Idle Timeout to your preferred value:
    • Never (default) - Connections are kept alive indefinitely
    • 5 minutes - Recommended for serverless databases
    • 10 minutes
    • 15 minutes
    • 30 minutes
    • 1 hour

How It Works

When the idle timeout is enabled:

  1. Timer starts when a query completes and the editor becomes idle
  2. Timer resets each time you execute a query
  3. Connection releases automatically when the timeout expires

Handling Uncommitted Changes

If you have uncommitted changes when the timeout expires (auto-commit is off):

  1. A warning notification appears showing the remaining time
  2. The timeout is extended by the same period to give you time to respond
  3. You can click Cancel to keep the connection and reset the timer
  4. If the grace period expires, changes are automatically rolled back and the connection is released

The grace period gives you time to commit or rollback your changes before the connection is released.

Database TypeRecommended Timeout
Redshift Serverless5 minutes
Snowflake5-10 minutes
BigQuery5-10 minutes
Databricks5-10 minutes
Provisioned databasesNever (default)

For provisioned databases where you pay a fixed cost regardless of queries, the default “Never” setting is appropriate and provides the best user experience.

Output Logging

When connections are released due to inactivity, DBCode logs the event to the Output panel:

  • Clean release: Connection: Released idle pinned connection for 'myfile.sql' after 5 minute(s)
  • With uncommitted changes: Connection: Released idle pinned connection for 'myfile.sql' after grace period (2 changes rolled back)