Drop / Recreating Objects

Some objects (such as indexes) have limited ability to have their definitions altered once they have been created.

The definition of these objects can only be resynced by dropping and recreating the object.

AQT will do this if:

• your database has been configured (within AQT) to use drop / recreate for this object
• the option Allow drop / redefine of index and other objects has been selected

You may wish to de-select Allow drop / redefine of index and other objects if your table has a large number of rows so that the recreation of the index would be a time-consuming process.

AQT will not use drop / recreate for tables. Your data is not at risk.

When recreating indexes, retain existing name

When AQT redefines an object (such as an index) it has a choice of which name to use for the object:

• the existing name for the object
• the name of the object being resynced to

Example:

suppose you have indexes:

• COMP.INDEX_CUST01 in Database1
• COMP.INDEX_CUST_UNIQ in Database2

As these indexes are on the same columns, AQT will deem them to be the "same" index. However some of the other attributes of the indexes (such as Unique flag) may be different.

To resync their definition, AQT may choose to drop and recreate COMP.INDEX_CUST_UNIQ to make it the same as COMP.INDEX_CUST01.

When recreating COMP.INDEX_CUST_UNIQ what name shall AQT use? There are two choices:

• COMP.INDEX_CUST_UNIQ (the same name the index was called previously)
• COMP.INDEX_CUST01 (the name of the index being resynced to)

When the When recreating indexes, retain existing name option is selected, AQT will use the first choice.