Disk Usage
functionalThe selected database's file layout - logical files, size, max, and growth.
Opened from a database, Disk Usage shows just that database's file layout:
each logical file, its type, physical path, current size, maximum size (blank when
unlimited), and growth setting rendered as a percentage or a fixed megabyte step. The
per-file view reads sys.database_files on SQL Server and Azure SQL. On
engines that do not expose a file layout, the tool shows the per-database sizes
overview instead of an empty tab.


Opening it
- In the explorer, right-click the database you care about.
- Choose Tools › Disk Usage.... If that database is on a different connection, or is not the current database, SQLly switches to it first, so the numbers are always for the node you clicked.
- Press Refresh to re-read the sizes at any time.
Disk Usage... in the command palette opens the server-wide view rather than this one. The dialog can pop out into its own window, which is handy when you want to keep an eye on a file while a load or rebuild runs in a query tab.
Reading the Files tab
| Column | What it means |
|---|---|
logical_name | The file's logical name - the one you would use in ALTER DATABASE ... MODIFY FILE. |
type_desc | ROWS for data files, LOG for the transaction log, and so on. |
physical_name | The path of the file on the server. |
size_mb | Current allocated size, in MB. |
max_size_mb | The growth ceiling in MB, or blank (NULL) when the file can grow without limit. |
growth | The autogrow step: a percentage such as 10%, or a fixed step such as 64.0 MB. |
Files are listed by type, then name, so the data files come first and the log follows. A
typical use is checking an unexpectedly large log: if size_mb is far above the
data files and growth is a small fixed step, the log has been autogrowing in many small
increments.
What other engines show
- ClickHouse - the Files tab lists the server's storage disks from
system.disksinstead: name, type, path, used space, and total space. Growth is blank. - PostgreSQL, MySQL and MariaDB - no per-file layout, so you get the per-database sizes overview (size and owner on PostgreSQL; data, index, and free MB per schema on MySQL and MariaDB).
- SQLite and libSQL / Turso - the database's size, reclaimable free-list space, page count, and page size.
- DuckDB - one row per attached database from
pragma_database_size(): size, reclaimable space, WAL size, and memory use. - Oracle Database - the space your own schema's segments use, per tablespace, split into table, index, and LOB MB.
- Redis - memory per logical database: key and expiry counts, plus an estimate scaled from a bounded
MEMORY USAGEsample (up to 200 keys per database), with the largest key found.
The full per-engine column list for the overview is on the server Disk Usage page.
Safety and limits
Disk Usage is strictly read-only: it runs SELECT queries over
the engine's catalog and never resizes, shrinks, or changes growth settings. The footer says
so, along with the row count. To change a file, write the ALTER DATABASE yourself
in a query tab.
On PostgreSQL, databases your login cannot connect to show a blank size rather than failing the whole list. If a query does fail, for example on missing permissions, the engine's error text is shown in the pane.