Académique Documents
Professionnel Documents
Culture Documents
Explicit Restructures.
Implicit Restructures:
Analytic Services initiates an implicit restructure of the database files after an outline is
changed using Outline Editor or Dimension Build. The type of restructure that is performed depends
on the type of changes made to the outline:
✟ Dense restructure: If a member of a dense dimension is moved, deleted, or added, Analytic
Services restructures the blocks in the data files and creates new data files. When Analytic
Services restructures the data blocks, it regenerates the index automatically so that index
entries point to the new data blocks. Empty blocks are not removed. Analytic Services marks
all restructured blocks as dirty, so after a dense restructure you need to recalculate the
database. Dense restructuring is the most time-consuming of the restructures and, for large
databases, can take a very long time to complete.
✟ Sparse restructure: If a member of a sparse dimension is moved, deleted, or added, Analytic
Services restructures the index and creates new index files. Restructuring the index is
relatively fast; the amount of time required depends on the size of the index.
✟ Outline-only restructure: If a change affects only the database outline, Analytic Services
does not restructure the index or data files. Member name changes, creation of aliases, and
dynamic calculation formula changes are examples of changes that affect only the database
outline.
Explicit Restructures:
When you manually initiate a database restructure, you perform an explicit restructure. An
explicit restructure forces a full restructure of the database. A full restructure comprises a dense
restructure plus removal of empty blocks.
Dense Restructures:
To perform a dense restructure, Analytic Services does the following:
1. Creates temporary files that are copies of the .ind, .pag, .otl, .esm, and .tct files. Each
temporary file substitutes either N or U for the last character of the file extension, so the
temporary file names are .inn, essxxxxx.inn, essxxxxx.pan, dbname.otn,
dbname.esn, and dbname.tcu.
2. Reads the blocks from the database files copied in step 1, restructures the blocks in memory,
and then stores them in the new temporary files. This step takes the most time.
3. Removes the database files copied in step 1, including .ind, .pag, .otl, .esm, and .tct
files.
4 Renames the temporary files to the correct file names: .ind, .pag, .otl, .esm, and .tct.
Sparse Restructures:
When Analytic Services does a sparse restructure (restructures just the index), it uses the
following files:
? essxxxxx.ind
? dbname.otl
? dbname.esm
To perform a sparse restructure, Analytic Services does the following:
1. Renames the dbame.esm file to dbname.esr
2. Renames the essxxxxx.ind files to essxxxxx.inm.
3. Creates new index files (essxxxxx.ind) to store index information that is changed by the
restructuring operation.
4 Removes dbname.esr and essxxxxx.inm created in 1.