SAQ - Seldom asked Questions
Create Database with Size forecasted for 3 Months or3 Years?
You are here: Home > SAQ - Seldom Asked Questions >
Create Database with Size forecasted for 3 Months or 3 Years?
Create database with Size forecasted for 3 Months or 3 Years?
- A discussion of several aspects
This topic is relevant for for databases which start with initially small size but grow within 1 to 3 years to hundreds of Gigabytes or Terra bytes.
This graphic illustrates a typical scenario: During the first years the customer base is growing fast, and as archiving of transaction history starts after 12 months, the disk space allocation growth x-square duing first year.
Afer 12 months, when transaction archiving is in place and all transactions older than 12 months are archived, the grows significantly reduces.
The 2 green lines indicate database size after 3 and 6 months.
It is obvious, that the size is magnitudes smaller than the size estimated after 1 year and 3 years.
As managing (cloning, backup, restore-tests) a small database is easier and faster than managing the fully-sized database, the idea to install the database with initially small size is obvious.
The following table provides pro- and contra arguments.
Utilizing “autoextend” feature allowing database files to grow on demand, is only an alternative
Copyright © 2005-2009 Mercury Consulting Limited.