Page History
...
| Object Type(s) | Migrated | Post Migration Notes |
|---|---|---|
| Connections |  | All connections are migrated, MSAS connections should be manually removed after migration. |
| MSAS, Cubes, Cube Dims, Tabular Cubes |  | 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 | | These legacy object sub-types are not available in RED 10 and aremigrated 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 | | All other object types not mentioned in the rows above are migrated as is. |
| Object Versions | | Previous object versions are not migrated. ThereThere are a few reasons for this: a). restoring
|
| WhereScape Callable Procedures* | | Since the inbuilt WhereScape Callable ProceduresRoutines are compiled on either SQL Server, Oracle or Teradata they can not be migrated* |
| Non-Script Based Loads | | 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 which was already script-based should function as is provided the appropriate table level Action Processing Script has been generated. |
| Info | ||
|---|---|---|
| ||
Any Procedures/Blocks or Scripts which called these |
...
callable routines before will continue to work but the outcomes will be applied to the original Source Metadata Repository and depending on the procedure being called will have no effect. Only the WhereScape Parameter Functions will still be of use as is post migration. Most use cases, outside of Parameter read/writes, will have involved a customized script or procedure, these should be reviewed to find the RED 10 equivalent and adjusted after migration. Note: Target Enablement Packs will handle legacy procedures that include the WhereScape Parameter read/write functions by synchronizing the dss_parameter table in the Target with the same table in the PostgreSQL metadata repository. In this way most procedures will continue to function as is after migration |
...
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.
...
. |
The Migration Tooling requires the following named connections in RED:
...