Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Performing Database Compaction/Reorganization Based on Performance and Availability

IP.com Disclosure Number: IPCOM000029731D
Original Publication Date: 2004-Jul-09
Included in the Prior Art Database: 2004-Jul-09
Document File: 2 page(s) / 33K

Publishing Venue

IBM

Abstract

Disclosed is the idea to utilize performance and availability information of a computing environment in making the decision as to when to perform a database compaction and/or reorganization. Using such a decision point to perform these tasks makes the environment more efficient and can improve overall performance and availability of a computing environment by performing these common database functions when system has the excess capability to do so as well as reducing an interference these functions may have during periods of high use or low availability.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Performing Database Compaction /Reorganization Based on Performance and Availability

Most Database Administrator's (DBA's) perform database compaction and/or reorganization on regular basis in order to improve efficiency and response time for users of their databases. The two most common techniques for deciding when to perform these actions are setting a schedule and setting thresholds. Both techniques have their advantages but neither takes into account whether the computing environment is busy or has low availability at the time when the action is taken. If the environment is busy or has low availability, execution of these tasks will likely worsen the environment's ability to perform efficiently and/or with a fast response rate while these tasks are executing.

It is of course possible for the DBA to use the scheduling technique and attempt to schedule these database actions when availability of the environment should be high, but this is not fool proof and requires the DBA and his/her peers to keep track of when these actions are scheduled as to not schedule other activates to occur at the same time within the environment. A good example of the scheduling difficulty is when another administrator schedules the removal of some required resource (i.e. disk drive) from the environment during the scheduled execution of the database compaction and/or reorganization task. In this example, the coordination and communication between the DBA and other administrators responsible for different components of the computing environment would be crucial to ensure that these database tasks are executed successfully. Using the technique contained within this disclosure to perform database compaction and/or reorganization eliminates the need for a DBA to schedule and keep track of possible conflicts of these tasks, as well as reduce the co...