This section contains the following topics:
Establishing Performance Requirements for Transactions
Determining How Often Transactions Will Be Executed
Identifying Access Requirements
Determining the Database Entry Point and Access Key for Each Transaction
Determining the Number of Entities in Each Relationship
Determining How Often Each Entity Will Be Accessed
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... |
---|---|
|
Refining the Physical Design (Chapter 12) |
|
Minimizing Contention Among Transactions (Chapter 14) |
|
Determining the Size of the Database (Chapter 15) |
Copyright © 2014 CA.
All rights reserved.
|
|