Versions Compared

Old Version 24

changes.mady.by.user Morgan Mackeson-Ellis

Saved on

compared with

New Version 25

changes.mady.by.user Morgan Mackeson-Ellis

Saved on

Key

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

...

Object Type(s)MigratedPost Migration Notes
Connections(tick) All connections are migrated, MSAS connections should be manually removed after migration.
MSAS, Cubes, Cube Dims, Tabular Cubes(error) Analysis Services Object Types are not migrated since RED 10 does not support them yet. 
Aggregate Dimension Join Table
Aggregate Fact Join Table
Aggregate Join Table
Fact Rollup
Fact Work Table
Permanent Stage
Model View
Fact View		(tick) 

These legacy object sub-types are migrated but assigned an new Custom Object Type in RED 10 of the same name. 

Objects of these types should be checked carefully in the Destination metadata.

All Other Object Types(tick) All other object types not mentioned in the rows above are migrated as is.
Object Versions(error) 

Previous object versions are not migrated. There are a few reasons for this:

  • Restoring to a version predating the migration would leave your object in an unusable state.
  • The size of the versioning tables in legacy repositories adds unnecessary delay to the migration.
  • It is better to start versioning again from scratch in the migrated repository.
WhereScape Callable Procedures*(error) 

Since the inbuilt WhereScape Callable Routines are compiled on either SQL Server, Oracle or Teradata they can not be migrated*

Non-Script-Based Loads(tick) 

Non-Script-based loads such as: ODBC, DB Link, SSIS and some File Load types are migrated however these load type will require a load script to be generated and therefore these types will need thorough testing post migrations.

Any load Load which was already script-based should function as is provided the appropriate table level Action Processing Script has been generated.

Non-Script-Based Exports(tick) 

Non-Script-Based Exports will require an Export script to be generated and therefore these types will need thorough testing post migrations.

Any Export which was already script-based should function as is, provided the appropriate Export level Action Processing Script has been generated.

...