Connections

A connection tells SQL Explorer how to reach one database server. Keep as many as you like, grouped into folders, and switch between them from the connection tree.

Adding a connection

Click New connection in the connection tree.
Pick the engine — the provider decides which fields you see.
Fill in host, port, database and credentials (or a file path for SQLite).
Test the connection, then Save. It appears in the tree, ready to expand.

Supported engines

Built in with the app:

SQL Server, MySQL / MariaDB, PostgreSQL, SQLite — full SQL engines with schema browsing, DDL and (except SQLite) user management.

Installable as first-party plugins from the Plugin Store:

MongoDB, Redis, DragonflyDB, Elasticsearch — browse and query with each engine's native query language.

Any other engine can be added as a provider plugin.

Browsing the schema

Expand a connection to walk a lazy schema tree: server → database → schema → tables / views / routines, with indexes, foreign keys and triggers under each table. Everything loads on demand, so large servers stay responsive. System databases are hidden by default — turn on Show system databases in Settings to include them.

Credentials & storage

Connection details are stored locally, and secrets (passwords) are kept in your operating system's secure credential store — never in plain text and never on any server. You can add an optional master password in Settings to encrypt stored secrets behind a single app password.

SQL Explorer needs no account and talks to no server of ours — connections and credentials stay on your machine.

Editing or removing

Right-click a connection to edit, duplicate or remove it. The right-click menu also sets a connection's AI access level.