Skip to content
ENExplore Calculators

Database Storage Estimate

Free Database Storage Estimate calculator with clear step-by-step results.

About Database Storage Estimate

Row count times average row size gives heap size, but indexes routinely add 30-60% on top and are what usually breaks a storage forecast. Compounding row growth over the projection period gives the figure to provision volumes and backup capacity against.

Formulas

Current size

Bytes = rows x average row bytes x (1 + index overhead)

Projected size

Projected = rows x (1 + monthly growth)^months x row bytes x (1 + index overhead)

Worked example

With the default values below, Database Storage Estimate returns Projected size at the end of the period of 2.626. Change any input above and every figure here is recalculated in your browser.

Inputs used

Rows in the tableminimum 0
5,000,000
Average row sizeminimum 1 B
180 B
Index overheadaccepts 0–300 %
45 %
Monthly row growthaccepts 0–100 %
6 %
Months to projectaccepts 1–120
12

Results

Projected size at the end of the period
2.626 GB
Current size including indexes
1.305 GB
Table data alone
0.900 GB
Projected row count
10,060,982 rows

Step by step

  1. 1Values used
  2. 2Current size
  3. 3Projected size
  4. 4Projected size at the end of the period= 2.626 GB
  5. 5Current size including indexes= 1.305 GB
  6. 6Table data alone= 0.900 GB
  7. 7Projected row count= 10,060,982 rows

Assumptions and limits

  • The result is derived only from the 5 inputs listed above. Anything not among them is not part of the calculation.
  • In particular, this calculator does not take inflation, tax, fees or charges or compounding frequency into account.
  • Figures are rounded for display to 3 decimal places, so totals built from several rounded parts can differ slightly from the unrounded arithmetic.

How these calculators are built and tested is described on the Methodology page. If a figure looks wrong, please report it.

Frequently Asked Questions

How do I measure average row size?

Divide the table's on-disk heap size by its row count using your engine's catalog views. Estimating from column types ignores per-row headers, alignment padding and page free space.

Does this cover WAL and backups?

No. Transaction logs, point-in-time recovery archives and full backup copies commonly need one to three times the live data size again.

Related Calculators

Database Storage Estimate | Calcrivo