Managing database transactions
When you need to reduce load from the local or remote database, keep these guidelines in mind:
- For large tables (over 500 records) that are read by the application, indexing the tables reduces the access time and impact on system performance. However, if tables are not indexed effectively, performance problems may remain.
- The insert (add) record operation is a much faster operation than the update (change) operation. One way to replace a change record with an add record is to add records to a table during the normal call hours and write a shell routine using SQL*PLUS to summarize and delete records during nonpeak hours.
- Encapsulating common database queries (those requiring multiple accesses on a single table or accesses from multiple tables) with SQL*Views reduces the number of transactions.
- Keep in mind that each call data event is a unique record in more than one table. Therefore, every time a call data event is accessed, the database table is updated at the end of the call.
