SQLly logoSQLly
// databases

The databases SQLly connects to

Ten engines - from SQL Server and PostgreSQL to DuckDB, ClickHouse and Redis - connect today through drivers built into SQLly, on macOS, Windows and Linux. Counting the hosted and compatible services below, that is 30 engines in all. Pick yours to see exactly what works on it, how to connect, and what doesn’t apply.

Pick your database

TDS · SQL Server family

SQL Server

The deepest engine: Entra ID sign-in, Query Store, SQL Agent, Extended Events, and the guided designers.

SQL Server in SQLly β†’ PostgreSQL wire

PostgreSQL

EXPLAIN ANALYZE plans, pg_stat_statements, roles and grants, Procedure Mode - plus Supabase, Neon, RDS and friends.

PostgreSQL in SQLly β†’ MySQL wire

MySQL

EXPLAIN ANALYZE plans, Performance Schema insights, accounts and privileges, and PlanetScale, TiDB, RDS and Aurora.

MySQL in SQLly β†’ MySQL wire · MariaDB dialect

MariaDB

Its own engine, not a MySQL alias: ANALYZE FORMAT=JSON plans, MariaDB activity and account queries.

MariaDB in SQLly β†’ In-process file

SQLite

Open a .sqlite or .db file directly: row editing, EXPLAIN QUERY PLAN, VACUUM and integrity checks.

SQLite in SQLly β†’ In-process file · analytics

DuckDB

Built in, nothing to install: Parquet and CSV queries, EXPLAIN ANALYZE plans, row editing, schema compare.

DuckDB in SQLly β†’ HTTP interface · analytics

ClickHouse

Streams over the HTTP interface: index-pruning plans, query-log insights, live queries with Kill, BACKUP / RESTORE.

ClickHouse in SQLly β†’ Oracle Net

Oracle Database

PL/SQL scripts with DBMS_OUTPUT, EXPLAIN PLAN, session monitor with kill, and statistics maintenance.

Oracle Database in SQLly β†’ HTTP · SQLite dialect

libSQL / Turso

Turso Cloud or your own sqld: token sign-in, SQLite dialect, schema compare and history, integrity checks.

libSQL / Turso in SQLly β†’ RESP · key-value, not SQL

Redis

Not SQL: redis-cli commands in a query tab, a key browser by prefix, INFO, CLIENT LIST and the slow log.

Redis in SQLly β†’

What works where

SQLly enables or disables each tool per engine from one capability matrix, and this table is that matrix. Each engine’s page has the detail - which statement a plan uses, or why a tool doesn’t apply.

SQLly tools by database engine
Tool SQL Server PostgreSQL MySQL MariaDB SQLite DuckDB ClickHouse Oracle Database libSQL / Turso Redis
Explorer, IntelliSense and hover cards Yes Yes Yes Yes Yes Yes Yes Yes Yes Partial
Edit rows in the results grid Yes Yes Yes Yes Yes Yes No No No No
Estimated execution plans Yes Yes Yes Yes Yes Yes Yes Yes Yes No
Actual (executed) plans Yes Yes Yes Yes No Yes No No No No
Activity Monitor Yes Yes Yes Yes No No Yes Yes No Yes
Query Insights Yes Yes Yes Yes No No Yes No No Yes
Server Dashboard Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Disk Usage and Object Browser Yes Yes Yes Yes Yes Yes Yes Yes Yes Partial
Maintenance menu Yes Yes Yes Yes Yes Yes Yes Yes Yes No
Schema Compare and Schema History Yes Yes Yes Yes Yes Yes Yes No Yes No
Data Compare Yes Yes Yes Yes Yes Yes Yes No Yes No
Data Transfer Yes Yes Yes Yes Yes Yes Yes No No No
Test Data Generator Yes Yes Yes Yes Yes Yes Yes No Yes No
Table Structure Editor Yes Yes Yes Yes Yes Yes Yes No Yes No
Index Analyzer Yes Yes Yes Yes No No No No No No
Security editor (users, roles, grants) Yes Yes Yes Yes No No Partial No No No
Backup / Restore Yes Yes Yes Yes No No Yes No No No
Create and drop database dialogs Yes Yes Yes Yes No No No No No No
Procedure Mode Yes Yes No No No No No No No No
SQL Agent, Extended Events and guided designers Yes No No No No No No No No No
SSH tunnels, proxies and Kubernetes port-forward Yes Yes Yes Yes No No Yes No Yes Yes
Read-only connections Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Auto-rollback safety wrap Yes Yes Yes Yes Yes Yes No Yes Yes No

Hosted and compatible engines

These services speak the PostgreSQL, MySQL or Redis protocol and are choices in SQLly’s connection editor in their own right, with the right port and encryption default and a note on anything that differs. Azure SQL Database is covered on the SQL Server page.

  • Azure SQL Database
  • CockroachDB
  • YugabyteDB
  • Amazon Aurora PostgreSQL
  • Amazon RDS for PostgreSQL
  • Azure Database for PostgreSQL
  • Google Cloud SQL for PostgreSQL
  • Neon
  • Supabase
  • Amazon Aurora MySQL
  • Amazon RDS for MySQL
  • Azure Database for MySQL
  • Google Cloud SQL for MySQL
  • PlanetScale
  • TiDB
  • Valkey
  • KeyDB
  • DragonflyDB
  • Amazon ElastiCache
  • Amazon MemoryDB

Modeled, not connected yet

SQLly’s engine model already describes these - dialect, identifier quoting, row limits and type mappings - but they don’t have live connectors, so you can’t connect to them from the app today.

  • IBM Db2
  • IBM Informix
  • Microsoft Access
  • Snowflake
  • Databricks SQL
  • Google Cloud Spanner
  • Teradata
  • SAP HANA

The full engine reference lives in the docs under Supported databases.

Questions

Which databases does SQLly support?

SQLly connects natively to 30 engines. The first-party ones are SQL Server and Azure SQL, PostgreSQL, MySQL, MariaDB, SQLite, DuckDB, ClickHouse, Oracle Database, libSQL / Turso and Redis. The connection editor also has labels for compatible services: CockroachDB, YugabyteDB, Amazon Aurora and RDS, Azure Database for PostgreSQL and MySQL, Google Cloud SQL, Neon, Supabase, PlanetScale, TiDB, Valkey, KeyDB, DragonflyDB, Amazon ElastiCache and Amazon MemoryDB.

Do I need to install database drivers?

No. SQLly's drivers are built in, and DuckDB and SQLite run inside the app. The one exception is Oracle Database, which needs Oracle's free Instant Client installed on your machine. If you want vendor-format dumps, SQLly can also drive pg_dump and mysqldump when they are installed.

Is SQLly free?

SQLly has a free tier for hobbyists and side projects: two saved servers with unlimited databases on each and one cloud account, with a reminder to pay about every five hours. Annual and Lifetime licenses lift the limits. Organizations with more than 100 employees may not use the free tier.

Which databases does SQLly not connect to yet?

IBM Db2, IBM Informix, Microsoft Access, Snowflake, Databricks SQL, Google Cloud Spanner, Teradata and SAP HANA are described in SQLly's engine model, so it knows their dialects and types, but they do not have live connectors yet.

// try it yourself

Bring your databases home to the pig

SQLly is free to start on macOS, Windows and Linux, with no account required.

⬇ Download SQLly - it’s free Compare SQL clients