International Business Machines Corporation

Thomas Ritter

Namik Hrle

Amit Bendakovsky

Oliver Augenstein

Andreas Uhl

A mechanism is provided for reorganizing a source index tree of a database table resulting in a target index tree of the database table is provided. A backup process reads source leaf pages of the source index tree in a logical order defined by a sequence of index keys. The logical order can be different from a physical order of the source leaf pages defined by a sequence of respective storage locations. The backup process constructs target leaf pages of the target index tree maintaining the logical order. A restore process constructs target non-leaf pages of the target index tree based on the distribution of the index keys among the constructed leaf pages and stores the target leaf and non-leaf pages.

Database backup and restore with integrated index reorganization

According to an embodiment of the present invention, a method for reorganizing a source index tree of a database table resulting in a target index tree of the database table is provided. A backup process reads source leaf pages of the source index tree in a logical order defined by a sequence of index keys. The logical order can be different from a physical order of the source leaf pages defined by a sequence of respective storage locations. The backup process constructs target leaf pages of the target index tree maintaining the logical order. A restore process constructs target non-leaf pages of the target index tree based on the distribution of the index keys among the constructed leaf pages and stores the target leaf and non-leaf pages.

A method and system for preventing redundant indexes in a database management system (DBMS). A received create-index command specifies a new index to be created for retrieving data from a table created by the DBMS and a redundancy check to be performed for the new index in conjunction with an action parameter in the create-index command. If the action parameter includes a REPORT value, each redundant index is stored and/or displayed and the new index is created. If the action parameter includes a PREVENT value and an existing index is redundant in view of the new index and the new index is not redundant in view of the existing index, the existing index is deleted and the new index is created. If the action parameter includes a PREVENT value and the new index is redundant in view of an existing index, the new index is not created.

Growing community of inventors

Herrenberg, Germany

Thomas Ritter