Minimizing Contention Among Transactions › Minimizing Contention

Minimizing Contention

Guidelines

You can reduce the likelihood of bottlenecks resulting from area and entity occurrence contention by making appropriate changes to the physical database design. To make intelligent design decisions to reduce contention, you must first identify potential bottlenecks.

Chapter 10, "Identifying Application Performance Requirements" showed you how to determine:

• The priority of each business transaction
• The frequency of execution of each transaction
• The frequency of access of each entity

By examining this information closely, you can identify potential bottlenecks in the physical database. For example, if you know that two different database entities will be accessed often, you can assign these entities to different areas to avoid area contention. Additionally, you can schedule the execution of high-priority programs to reduce the likelihood of contention with other programs.