Previous Topic: Preliminary Data Structure Diagram for Commonweather CorporationNext Topic: Establishing Performance Requirements for Transactions


Identifying Application Performance Requirements

This section contains the following topics:

Overview

Establishing Performance Requirements for Transactions

Prioritizing Transactions

Determining How Often Transactions Will Be Executed

Identifying Access Requirements

Determining the Database Entry Point and Access Key for Each Transaction

Projecting Growth Patterns

Determining the Number of Entities in Each Relationship

Determining How Often Each Entity Will Be Accessed

Overview

After creating the preliminary data structure diagram, you need to interview company employees who can help you determine the application requirements for the database so that you can refine that database structure.

Performance and storage requirements

As you gather information from users, you need to identify both the performance and storage requirements of the system:

The requirements of the system determine how you should design the physical database model. For example, the requirements of a particular application can help you to define the page size for a database area.

Making design decisions

You will use the information that you gather at this stage in the physical design process to make several design decisions later on, as shown below.

Information gathered in this chapter

Used in...

  • Performance requirements for transactions
  • Transaction priorities
  • Access requirements
  • Database entry points and access keys

Refining the Physical Design (Chapter 12)

  • How often each transaction will be executed
  • How often each entity will be accessed

Minimizing Contention Among Transactions (Chapter 14)

  • Projected growth patterns
  • Number of entity occurrences in each relationship

Determining the Size of the Database (Chapter 15)