For example, online transaction processing (OLTP) systems usually have
a larger number of users performing smaller transactions, while data warehouses
usually have a smaller number of users performing larger queries.
What are the expected size and number of database objects?
How large will these objects be initially and what growth rates do you expect?
What are the access patterns for the various database objects?
Some objects will be more popular than others. Understanding the volume and
type of activity in the database is critical to planning and tuning your database.
Some people employ a so-called CRUD matrix that contains Create, Read,
Update, and Delete indicators, or even estimates for how many operations will
be performed for each key object used by a business transaction. These estimates
may be per minute, per hour, per day, or for whatever time period makes
sense in the context of your system. For example, the CRUD matrix for a simple
employee update transaction might be as shown in Table 3-1, with the checkmarks
indicating that each transaction performs the operation against the object
shown.
Pages:
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154