Versions Compared

Old Version 2

changes.mady.by.user Kavitha Thangaswamy

Saved on

compared with

New Version 3

changes.mady.by.user Pamela Totas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The best way to think of Data Mart migration is that it is model migration. While models are clearly meant to move from a source to a target environment as part of the software development life cycle, there are likely to be other Mart characteristics like scheduling and users access controls that are not shared among environments, and should not migrate. The following table shows what is and is not migrated by Migration Wizard.

Component

Migrated

Not Migrated

Mart Tables



Table Data


X

Manage Mart Section



Administration/Config Settings


X

Administration/Archive Settings


X

Schedules


X

Snapshots


X

Extensions

X


Model Information
The Business Dates table does not migrate.



Definition tab

X
(Except Schedule to Run check boxes)


Fields tab

X
(Mappings to performance models are migrated, but not the models themselves.)


Field Schedules tab


X

Filters/Mapping tab

X


Funds (Entities) tab


X

Access tab


X

Currencies tab

X


Execution Log section



Filter Settings


X

View Mart Data section



View Settings


X

Underlying Meta Data



Field Attributes

X


Classifications (regular dictionaries)

X


Filter Rules

X


Range Rules

X


Codes/Code Values

X


Performance Dictionaries


X
Use direct migration of performance calculation profile, and run that profile to create the performance dictionary. You may not migrate a model that is mapped to a performance dictionary until that dictionary is present in the target environment.

Source Rules


X
Use direct migration of the source rule.