Database Growth Calculator
Project compound plus flat database growth, find the doubling time and the month the allocated storage runs out.
Inputs
Growth proportional to existing data — user rows, orders, events.
Growth independent of size — a fixed feed, log or import.
Projected Size
1,873.7GB
Months Until Storage Is Full
14months
Reported as 0 when the volume never fills inside a 600-month horizon.
Doubling Time
11.9months
Allocated Storage Used
187.4%
Projected Size
2 TiB
Projected Monthly Storage Cost
$215.47
Step by step
Values used
Current database size = 400 GB; Compound monthly growth = 6 %; Flat monthly additions = 5 GB/month; Allocated storage = 1,000 GB; Project ahead = 24 months; Storage price = 0.1150 $/GB-month
Database Growth
size after m months = current × (1 + r)^m + flat × ((1 + r)^m − 1) ÷ r; doubling time = ln(2) ÷ ln(1 + r).
Projected Size
= 1,873.7 GB
Months Until Storage Is Full
= 14 months
Doubling Time
= 11.9 months
Allocated Storage Used
= 187.4
Projected Size
= 2,011,818,240,369
Projected Monthly Storage Cost
= 215.47
How it works
Real databases grow two ways at once, so the projection combines a geometric term for size-proportional growth with an annuity term for the fixed monthly feed. Doubling time comes from the compound rate alone and is the figure worth remembering: 6% a month doubles the database in under a year, which is why linear extrapolation from a single month always under-predicts. The storage rate is an editable input with a realistic us-east-1 default, so confirm the current price with AWS for your region. Storage runway is the input to the only two decisions that matter here — when to grow the volume and when to start archiving — and both need lead time measured in months, not the week before the volume fills.
Formula
Database Growth
size after m months = current × (1 + r)^m + flat × ((1 + r)^m − 1) ÷ r; doubling time = ln(2) ÷ ln(1 + r).
- 600
- Month horizon the runway search stops at, about fifty years
- r
- Compound monthly growth rate as a fraction
- flat
- Fixed GB added each month regardless of current size
- doubling time
- Months for the compound component alone to double the data
Frequently Asked Questions
How is Database Growth calculated?
size after m months = current × (1 + r)^m + flat × ((1 + r)^m − 1) ÷ r; doubling time = ln(2) ÷ ln(1 + r). Real databases grow two ways at once, so the projection combines a geometric term for size-proportional growth with an annuity term for the fixed monthly feed. Doubling time comes from the compound rate alone and is the figure worth remembering: 6% a month doubles the database in under a year, which is why linear extrapolation from a single month always under-predicts. The storage rate is an editable input with a realistic us-east-1 default, so confirm the current price with AWS for your region.
Why does Database Growth matter?
Storage runway is the input to the only two decisions that matter here — when to grow the volume and when to start archiving — and both need lead time measured in months, not the week before the volume fills.
What values do I need to enter?
This calculator takes 6 inputs: Current database size, Compound monthly growth, Flat monthly additions, Allocated storage, Project ahead, Storage price. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Why does the flat component need a different formula?
A fixed monthly addition also compounds once it lands, because next month's percentage growth applies to it too. The annuity term ((1 + r)^m − 1) ÷ r accumulates each deposit with the growth it earns after arriving, which simple multiplication misses.