System databases & schemas

functional

Choose 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.

WhatChoicesDefault
System databases
master, tempdb, model, msdb; PostgreSQL template0/template1/postgres
Group into a System Databases folder / show inline with user databases / hiddenFolder
System schemas
sys, INFORMATION_SCHEMA, guest, db_* roles, PostgreSQL pg_* & crdb_internal
Group into a System Schemas folder / hidden / only show if not emptyFolder

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.
The schema setting needs schema folders. System-schema placement applies when Schema display is set to Group by schema (see Schema tree). In the default All schemas together view there are no schema folders to place; instead the Tables and Views folders list your own objects only - SQL Server reads them from 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, and msdb are system databases; sys, INFORMATION_SCHEMA, guest, and every db_* fixed-role schema are system schemas.
  • PostgreSQL and its relatives - template0, template1, and the postgres maintenance database count as system databases. If you keep real work in postgres, choose Show inline so it sits with the rest. Any schema starting pg_, plus information_schema and CockroachDB's crdb_internal, counts as a system schema.
  • MySQL, MariaDB, and ClickHouse - their built-in databases (such as information_schema, mysql, performance_schema, and sys, or ClickHouse's system) 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.