To minimize the time and storage needed for database restructures, if a database outline changes frequently, analyze the outline and the types of outline changes.
Levels of restructuring for aggregate storage databases, listed from most to least expensive (in regard to time, storage, and data):
Table 235. Aggregate Storage Restructuring Levels
Clears data and aggregate views, and performs full outline restructure | User must reload input (level 0) data, select the aggregate views, and rerun the database aggregation. | |
| Clears aggregate views. and performs full outline restructure | Storage requirement is up to three times the size of the database file (.dat file). User must select the aggregate views and rerun the database aggregation. |
Perform a change that is not included in other categories; for example, delete or move a member, or add a member that is not the last of its siblings | Storage requirement is up to three times the size of the database file (.dat file). | |
Perform a light restructure change (described below) to an alternate hierarchy or an attribute dimension | Rebuilds all aggregate views that are based on attribute dimensions or alternate hierarchies | Storage requirement is up to three times the size of the affected views. Such aggregate views normally exist only if you used query tracking to select views based on usage. See Selecting Views Based on Usage. |
On nonattribute dimensions without stored level 0 members (for example, all level 0 members are shared or have formulas), add a child or child branch without changing the number of levels in the hierarchy. On nonattribute dimensions with stored level 0 members:
|