What happens when restructuring the ESSBASE outline

Essbase allows you to perform restructure in three ways,

• Outline Restructure,
• Sparse Restructure,
• Dense Restructure.

The Essbase objects such as page file, index file etc will change according to your selection, the changes first done in temporary files, after completion of restructuring the temporary files will be turned to original files,

Available temporary files in Essbase:
otn/otm/otu : Outline file.

• pan : Page file (each page file size is 2GB, the total number of page file depends on the data)
• inn : Index file (this is only file)
• esn : Essbase kernel file
• tcu : Transaction control file.
• esr : Essbase root file
• ddm/ddn : Partition file

Lets discuss what happen according to the restructuring type:

Outline Restructure : I could say this is only the type of Restructuring in which only outline file will get impact, since this happens when outline has changes in Aliases, Member formula, Attribute members and others.

Sparse Restructure : As sparse dimension members creates the Indexes, so while performing the Sparse restructuring only the Index file will change along with Outline file.

Dense Restructure : I could say this restructure as FULL restructure since it consider all the changes in the outline, here all files Outline, Index and Page file will change.
The remaining files such as Partition file (If available), Essbase Kernel file, Transaction control file and Essbase root file will be common in all the types restructures.

Happy learning and thanks for all who supported to write this post :)