All Products
Search
Document Center

Data Lake Formation:Storage overview

Last Updated:Mar 26, 2026

The storage overview shows the physical disk footprint of your data catalog, including all object versions. Use it to understand storage resource usage and identify optimization opportunities. Data is updated once per day by a batch job (T+1).

How storage sizes differ

Storage sizes differ depending on where you look:

Location What it includes
Partition list Only valid data files referenced by the latest snapshot — active, queryable, and not yet purged
Storage overview Valid data files + data from unexpired historical snapshots + orphan files + file fragments from OSS multipart uploads

The total size shown in the storage overview is usually greater than or equal to the sum of all partition sizes in the partition list. For example, if the storage overview shows 100 GB and the partition list totals 60 GB, the 40 GB difference comes from unexpired historical snapshots, orphan files, and file fragments from OSS multipart uploads that have not been purged.

View storage overview

Catalog

  1. Log on to the DLF console.

  2. In the left navigation menu, click Catalogs, and then click the name of your catalog.

  3. Select the Storage Overview tab.

The tab shows storage data for the current catalog.

Database

  1. Log on to the DLF console.

  2. In the left navigation menu, click Catalogs, and then click the name of your catalog.

  3. In the Databases section, click your database name.

  4. Select the Storage Overview tab.

The tab shows storage usage for the current database.

Table

  1. Log on to the DLF console.

  2. In the left navigation menu, click Catalogs, and then click the name of your catalog.

  3. In the Databases section, click your database name.

  4. Click a table name.

  5. Select the Storage Overview tab.

The tab shows physical storage data for the current table.

What's next

To reduce the gap between physical storage and queryable data, expire old snapshots and remove orphan files from your tables. For large gaps, also check for incomplete OSS multipart uploads, which leave behind file fragments until they are aborted or expire.