ODBC for QuickBase

Application Note for QuNect ODBC for QuickBase

Turn On ODBC Connection Pooling in Windows ODBC Administrator

ODBC connection pooling allows Windows to reuse existing ODBC connections instead of creating a new connection every time your application opens one. For workloads that open and close many short-lived connections, pooling can reduce connection setup overhead and improve throughput.

Important: Connection pooling is configured in the Windows ODBC Administrator and is applied per ODBC driver, not per DSN.

How to enable pooling
1. Close applications that are actively using the driver.
2. Open the correct ODBC Administrator for your application bitness:
  • 64-bit apps: Start menu search for ODBC Data Sources (64-bit)
  • 32-bit apps: Start menu search for ODBC Data Sources (32-bit)
3. Go to the Connection Pooling tab.
4. Select QuNect ODBC for QuickBase in the drivers list.
5. Click Configure....
6. Choose Pool Connections to this driver.
7. Set the Timeout value (seconds) for how long an unused pooled connection is kept before it is released.
8. Click OK, then restart your application/service.

How to confirm it is helping
Run a representative workload and compare before/after behavior. You should see fewer new connection creations and better performance when your app frequently opens and closes connections. If needed, use QuNect ODBC for QuickBase API and SQL logging to compare activity patterns.

Trade-offs of connection pooling
Benefits
  • Lower latency for repeated connect/disconnect cycles.
  • Less connection setup overhead under concurrency.
  • Better throughput in service-style workloads.

Costs and risks
  • Connections can remain open longer, which may consume more server/session resources.
  • Long timeouts may keep stale connections around after network or credential changes.
  • Very short timeouts reduce stale-connection risk but also reduce pooling benefit.
  • For long-lived single-connection applications, pooling may provide little or no gain.

Recommended starting point
Enable pooling and start with a moderate timeout (for example, 60 to 180 seconds), then tune based on your workload and stability requirements.