TablePro provides a streamlined interface for managing all your database connections. This guide covers creating, organizing, and managing connections across different database types.
Color-code your connection for easy identification
Tag
Organize connections with custom tags
Read-Only
Toggle to prevent all write operations on this connection
Use colors to visually distinguish between environments (e.g., red for production, green for development). Enable Read-Only mode for production databases to prevent accidental writes.
For MySQL, MariaDB, and PostgreSQL connections, you can configure SSL/TLS encryption:
Field
Description
SSL Mode
Encryption mode (see table below)
CA Certificate
Path to Certificate Authority file (for Verify CA/Verify Identity modes)
Client Certificate
Path to client certificate file (optional)
Client Key
Path to client private key file (optional)
Available SSL Modes:
Mode
Description
Disabled
No SSL encryption (default)
Preferred
Use SSL if available, fall back to unencrypted
Required
Require SSL encryption, but don’t verify certificates
Verify CA
Require SSL and verify the server certificate against a CA
Verify Identity
Require SSL, verify CA, and verify the server hostname matches the certificate
For production databases, use Verify CA or Verify Identity mode for maximum security. For development servers, Required provides encryption without needing certificate files.
SSL/TLS is not available for SQLite connections (file-based, no network involved).
Switch between active or saved connections directly from the toolbar without returning to the Welcome screen:
Click the connection name button in the toolbar
A popover appears showing your active sessions and saved connections
Click any connection to switch to it immediately
Click Manage Connections… to open the full connection manager
The connection switcher popover is the fastest way to jump between databases during development. If the popover is already open, clicking the connection button again will dismiss it.
For MySQL, MariaDB, and PostgreSQL connections, TablePro sends a lightweight ping (SELECT 1) every 30 seconds to verify the connection is alive. SQLite connections are file-based and don’t require health monitoring.
When a health check detects a lost connection, TablePro automatically attempts to reconnect:
Attempt 1 — waits 2 seconds, then reconnects
Attempt 2 — waits 4 seconds, then reconnects
Attempt 3 — waits 8 seconds, then reconnects
If all three attempts fail, the connection enters an error state and you’ll see a Reconnect button in the toolbar.SSH tunnels have their own independent health monitoring and are automatically re-established if the tunnel process dies.
If auto-reconnect fails, click the Reconnect button (↻) in the toolbar to manually re-establish the connection. For SSH connections, this also recreates the SSH tunnel.
The toolbar status indicator shows the current connection state: green for connected, orange for reconnecting, and red for error/disconnected.
SQLite connections are file-based and don’t require health monitoring or auto-reconnect.