System databases & schemas
functionalChoose whether each engine's built-in objects are folded away, shown inline, or kept out of sight.
Every engine ships useful-but-rarely-visited places such as master,
tempdb, sys, INFORMATION_SCHEMA, and
PostgreSQL's pg_catalog. SQLly tucks them away by default, while
Settings › Data Model › Server Explorer lets you choose how
visible they should be.
| What | Choices | Default |
|---|---|---|
| System databases master, tempdb, model, msdb; PostgreSQL template0/template1/postgres | Group into a System Databases folder / show inline with user databases / hidden | Folder |
| System schemas sys, INFORMATION_SCHEMA, guest, db_* roles, PostgreSQL pg_* & crdb_internal | Group into a System Schemas folder / hidden / only show if not empty | Folder |
What each choice does
System databases
- Group into a System Databases folder - your databases come first, and the engine's own go into one folder at the end of the server's list. The folder only appears when the server actually has any.
- Show inline with user databases - everything in one list, in the order the server returns it.
- Hidden - system databases are left out of the tree entirely. You can still query them from an editor tab; this only changes what the explorer draws.
System schemas
- Group into a System Schemas folder - schema folders for your schemas, then one System Schemas folder holding the rest.
- Hidden - system schemas are not shown.
- Only show if not empty - system schemas sit alongside yours, but only the ones that actually contain objects. A schema whose object count the engine cannot report is treated as not empty, so nothing silently vanishes.
sys.objects, and PostgreSQL leaves out pg_catalog, information_schema, and the pg_toast and pg_temp schemas - so system objects never mix into your lists.Browsing system objects on purpose
Sometimes you do want the catalog. With Group by schema on, open
System Schemas on a SQL Server database and expand sys or
INFORMATION_SCHEMA: SQLly lists the catalog views that live there,
reading them from sys.all_objects because SQL Server leaves its own
shipped objects out of sys.objects. On PostgreSQL, a system schema
opened from the folder lists its relations the same way any schema does.
Engine differences
- SQL Server and Azure SQL -
master,tempdb,model, andmsdbare system databases;sys,INFORMATION_SCHEMA,guest, and everydb_*fixed-role schema are system schemas. - PostgreSQL and its relatives -
template0,template1, and thepostgresmaintenance database count as system databases. If you keep real work inpostgres, choose Show inline so it sits with the rest. Any schema startingpg_, plusinformation_schemaand CockroachDB'scrdb_internal, counts as a system schema. - MySQL, MariaDB, and ClickHouse - their built-in databases (such as
information_schema,mysql,performance_schema, andsys, or ClickHouse'ssystem) are not recognized by this setting today, so they are listed with your own databases whichever option you pick.
Changes take effect the next time a server or database is expanded. File engines - SQLite, libSQL / Turso, DuckDB - have no system databases to fold away, and a Redis connection shows its numbered logical databases and key-prefix folders instead of a schema tree.