24.12.2012 Views

ER/Studio - Embarcadero Technologies Product Documentation

ER/Studio - Embarcadero Technologies Product Documentation

ER/Studio - Embarcadero Technologies Product Documentation

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

USING <strong>ER</strong>/STUDIO > DEVELOPING THE PHYSICAL MODEL<br />

Planning for and Predicting Database Growth<br />

In order to ensure optimal database performance, it is important that you assess your storage needs and plan<br />

accordingly. This section will help you to do this and is comprised of the following topics:<br />

• Planning for Table and Index Storage<br />

• Predicting Table Growth<br />

Planning for Table and Index Storage<br />

Planning the storage of tables and indexes is best done during the physical design stage in order to improve<br />

performance and to streamline data administration tasks. When planning physical storage, carefully consider both the<br />

placement and size of tables and indexes. The performance of almost all database applications is I/O bound. To<br />

improve I/O throughput, physically separate tables that are frequently joined together. Also, separate tables from their<br />

indexes. The objective is to have the database read or write data in parallel as much as possible.<br />

Two key concerns of every database administrator are free space management and data fragmentation. If you do not<br />

properly plan for the volume and growth of your tables and indexes, these two administrative issues could severely<br />

impact system availability and performance. Therefore, when designing the physical model, consider the initial extent<br />

size and logical partition size.It<br />

As a starting point, estimate the size of each table and its indexes based on a projected row count. The Capacity<br />

Planning tool helps project the size of the databases given certain growth parameters. For databases that let you<br />

specify initial extent sizes, such as Oracle, set the initial extent size to the estimated size in order to avoid data<br />

fragmentation as the table grows. By keeping tables within a single extent, data access times decreases and table<br />

reorganization can be determined.<br />

Once you have determined the placement and sizes of the tables and indexes in your database, estimate the total size<br />

requirements of the database in order to avoid running out of free space for the database.<br />

Predicting Table Growth<br />

Capacity planning metrics can be recorded for each table so that proper sizing can be done before the table is<br />

implemented in a database.<br />

The Capacity Planning tab of the Table Editor helps predict change using metrics such as table row count, table<br />

growth rate, growth type, growth period and table maximum size.<br />

1 In the Data Model Explorer, double-click a table in the physical model.<br />

2 Click and then complete the Capacity Planning tab.<br />

TIP: Change the column Avg. Width and Percent Null values to more accurately predict the table<br />

growth.<br />

The growth predictions you make in the Table Editor display in the Capacity Planning utility and can be edited<br />

there.<br />

EMBARCAD<strong>ER</strong>O TECHNOLOGIES > <strong>ER</strong>/STUDIO® 8.0.3 US<strong>ER</strong> GUIDE 218

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!