Page History
...
The Migration Tooling requires a 'Custom Target' enabled license. This is because the tooling will use the Custom Target database type for loading into the destination PostgreSQL RED metadata database. For customers on a traditional SQL Server, Oracle or Teradata targets your license may need to be temporarily upgraded to support the migration by adding a Custom Target.
| License Fields | Values | Migration Requirements |
|---|---|---|
| Licensed Metadata Database Type(s) | SQL Server, Oracle, Teradata | One or more of SQL Server, Oracle or Teradata |
| Licensed Target Database Type(s) | SQL Server, Oracle, Teradata, Custom | 'Custom' at a minimum |
| Licensed Custom Target Database Type | MySQL | Any Custom Target Type (see the note that follows) |
| Info | ||
|---|---|---|
| ||
Licensed Custom Target Database Type is the label in your license given to your Custom target, this will be used for PostgreSQL targets during migration. This is just a display label for the underlying Custom target type. It could be set to anything in your own license and will be discernable in database type dropdowns by having a trailing '*'. So MySQL will appear as MySQL* in RED. For example: your license might have a label of Snowflake*, RedShift* or Synapse* but the underlying database type in RED is Custom. |
Migration Source Metadata
Source Metadata:
- A supported RED Metadata Repository on SQL Server, Oracle or Teradata which has a RED version of 8.6 or higher
- ODBC DSN and user with select permissions to the metadata database.
...