Capacity Planning | Database Design | VantageCloud Lake - Capacity Planning - Teradata VantageCloud Lake

When there is no legacy database to build on, capacity planning can be difficult. This is rarely an issue for contemporary users, because at least part of their corporate databases are typically maintained in electronic form. Much information in this section assumes you have a legacy system to draw on for making sizing estimations.

Capacity planning begins with making the most frequently accessed data available at all times. With the relatively low priced, large capacity disk storage units commonly used for data warehousing applications, the nature of the emphasis on this factor has changed from offloading as much historical data as possible to archival storage toward developing the capability of keeping all data forever online and accessible to the warehouse.

In a data warehouse that maintains massive quantities of history data, the volume of data is typically inversely proportional to its use. That is, there is an enormous amount of cool history data that is accessed lightly, and a relatively lesser volume of hot and warm data that is accessed frequently.

The following loose default definitions apply to the commonly described temperature bands.

The file system can change the compressed state of the data in an AUTOTEMP table at any time based on its temperature. Cylinders in an AUTOTEMP table become eligible for temperature-based block-level compression only when reaching or falling below the threshold defined for COLD temperature-based block level compression.

Temperature-based thresholds for the block-level compression of AUTOTEMP tables work as defined by the following table.

• Extended Data Lifetimes
• Cool and Icy Data
• Warm, Hot, and Very Hot Data