Essbase Studio performs several tasks when migrating a model from an Integration Services catalog to an Essbase Studio catalog.
The Essbase Studio migration utility first creates a folder with the same name as the model in Integration Services, and then it performs the migration.
An Integration Services model contains a star schema, which contains a subset of tables, as well as information about star schema joins. If a user has defined hierarchies, that information is also in the model.
To migrate this metadata to Essbase Studio, the migration utility performs the following steps:
A subfolder is created under the model folder in Essbase Studio for each of the tables in the star schema.
For each table column, a dimension element is created within each table folder. The caption and key binding for each dimension element reflects the table column.
For time dimension elements, the appropriate time transformations are applied and new dimension elements are created.
For each hierarchy defined in the Integration Services model, a corresponding hierarchy is created in the Essbase Studio model folder.
A minischema is created in Essbase Studio corresponding to the star schema of the Integration Services model so that all joins are migrated, including the self-joins for recursive hierarchies.