Skip to main content

Review Migration Scenarios

The topic outlines the process of migrating changes to default or custom database objects and ETL components within a data source or staging area from a lower to higher environment.

Prerequisites

Complete these steps before you start:

Export your data source or staging area (default)

  1. Go to Data Sources or Staging Area.
  2. Select Export.
  3. Choose Default.
  4. Select Export.

Import your data source or staging area (default)

  1. Go to Data Sources or Staging Area.
  2. Select Create.
  3. Set Type to Default.
  4. Upload the file you exported in the previous steps.
  5. Select Import.

Template Customizations

Database Objects and ETL Projects

Supported Scenarios

Migrating new database objects and ETL projects (default) 

Lower environment:

  1. Import the template from insightsoftware that contains new objects.
  2. Upgrade your data source or staging area to use the new template version:
    1. Go to Data Source or Staging Area.
    2. Select Edit.
    3. In the Overview tab, choose Latest Template Version.
    4. Select Save.
  3. Export the new objects:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select the added objects.
    5. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating modified database objects and ETL projects (default) 

Lower environment:

  1. Import the template from insightsoftware that contains modified objects.
  2. Upgrade your data source or staging area to use the new template version:
    1. Go to Data Source or Staging Area.
    2. Select Edit.
    3. In the Overview tab, choose Latest Template Version.
    4. Select Save.
  3. Export the changed objects:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select the modified objects.
    5. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating deleted database objects and ETL projects (default) 

Lower environment:

  1. Import the template from insightsoftware that has deleted objects.

  2. Upgrade your data source or staging area to use the new template version:
    1. Go to Data Source or Staging Area.
    2. Select Edit.
    3. In the Overview tab, choose Latest Template Version.
    4. Select Save.

  3. Export the removed objects:

    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select the deleted objects.
    5. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating renamed database objects and ETL projects (default) 

Lower environment:

  1. Import the template from insightsoftware that has renamed objects.

  2. Upgrade your data source or staging area to use the new template version:
    1. Go to Data Source or Staging Area.
    2. Select Edit.
    3. In the Overview tab, choose Latest Template Version.
    4. Select Save.
  3. Export the renamed objects:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select the renamed objects.
    5. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Sync 

Database Objects 

Supported Scenarios

Migrating new database objects (custom)

Lower environment:

  1. Create a new object in the database and add it to the application using custom sync:
    1. Go to Deployment tab.
    2. Select Sync > Custom.
    3. Choose All object option.
    4. Select one or more objects.
    5. Select Sync.
  2. Export the newly added objects:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select the added objects.
    5. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating modified database objects (custom and default)

Lower environment:

  1. Modify any object in the database by altering the columns, adding explicit where conditions etc., and sync the data source or staging area.
  2. Export the changed objects:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select the modified objects.
    5. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating deleted database objects - dropped from database (custom)

Lower environment:

  1. Drop custom object (e.g., table or view) in the database and then sync, it is also removed from the data source or staging area.
  2. Export the removed objects:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select the deleted objects.
    5. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating deleted database objects - deleted from application (custom)

Lower environment:

  1. Delete a custom object (e.g., table or view) from the application using the Delete button and then sync, the object is removed only from the data source or staging area.
  2. Export the removed objects:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select the deleted objects.
    5. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating renamed database objects (custom)

Lower environment:

  1. Rename a custom object (e.g., table or view) in the database, both objects with old and new name will be displayed in sync, sync both objects. Old object will be deleted from the application and new one will be added.
  2. Export the renamed objects:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select both objects with old and new name.
    5. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Unsupported Scenarios

Unsupported scenarios

Deleting a template object from data source or staging area (default)

A default object (object that is part of the imported template) cannot be deleted from the data source or staging area using the sync option and hence cannot migrate.

A default object (object that is part of the imported template) that has been dropped in the database will not be visible in the default sync screen and cannot be deleted from the data source or staging area using the sync option and hence cannot migrate.

Renaming the template object (default)

A default object (object that is part of the imported template) that has been renamed in the database directly, cannot be synced to the data source or staging area.

ETL Objects 

Key points to remember:

  • Only Projects, Jobs, Workflows and Dataflows are shown as part of the ETL Component hierarchy.
  • Search functionality is not supported in the ETL export screen. Browse manually to locate the ETL Components.

Supported Scenarios

Migrating new ETL projects (custom)

Lower environment:

  1. Add a new ETL Project in SAP Data Service and sync from custom sync All object view:
    1. Go to the Data Pipeline tab.
    2. Select Sync > Custom.
    3. Choose All object option.
    4. Select one or more projects.
    5. Select Sync.
  2. Export the added ETL components:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select ETL.
    5. Select the added components.
    6. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating a new Job, Workflow, or Dataflow which are added inside an ETL component - Project, Job or Workflow (custom and default)

Lower environment:

  1. Select the ETL Component - Job, Workflow, or Dataflow individually and sync to the data source.
  2. Export the added ETL components:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select ETL.
    5. Select the added components.
    6. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating a new Loop, Catch, Try, Conditional, or Script which were added inside an ETL Component - Job, Workflow, Dataflow (custom and default)

Lower environment:

  1. Select and sync the Job, Workflow or Dataflow to the data source.
  2. Export the added ETL components:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select ETL.
    5. Select the added components.
    6. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating a new ETL Component – Workflow or Dataflow which were added under Loop, Catch, Try or Conditional (custom and default)

Lower environment:

  1. Add a new ETL component (Workflow or Dataflow) under Loop, Catch, Try, or Conditional and select its parent ETL component – Project, Job, Workflow, or Dataflow. The parent will be shown as modified. Sync it.
  2. Export the added ETL components:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select ETL.
    5. Select the synced components.
    6. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating two added ETL components with the same name under the same parent ETL component (custom and default)

Lower environment:

  1. Select multiple ETL components (Workflow or Dataflow) with the same name under the same parent (Job, Workflow or Dataflow) and sync to the data source.
  2. Export the added ETL components:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select ETL.
    5. Select the added components.
    6. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating nested dataflows (custom and default)

Lower environment:

  1. Nested dataflows are supported for syncing. Select each of the nested dataflows individually or the parent component (Job, Workflow or Dataflow) and select Sync.
  2. Export the added or modified ETL components:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select ETL.
    5. Select the added or modified components.
    6. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating a modified ETL Component - Project, Job, Workflow, Dataflow, Loop, Catch, Try, Conditional, or Script (custom and default)

Lower environment:

  1. Select and sync the modified ETL Component - Project, Job, Workflow, Dataflow, Loop, Catch, Try, Conditional, or Script to the data source.
  2. Export the added ETL components:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select ETL.
    5. Select the modified components.
    6. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating deleted ETL Component - Project, Job, Workflow, or Dataflow from the data source only (soft-delete) (custom)

Lower environment:

  1. Select and sync the ETL Component - Project, Job, Workflow, or Dataflow that needs to be soft deleted to the data source.
  2. Export the added ETL components:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select ETL.
    5. Select the deleted component's parent – Project, Job, Workflow, or Dataflow.
    6. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating deleted ETL Component - Job, Workflow, Dataflow, Loop, Catch, Try, Conditional, or Script from the data source (after the component has been deleted in SAP Data Services Repository) (custom and default)

Lower environment:

  1. While the deleted ETL component from the SAP Data Services repository can be synced individually, we recommend syncing its parent (Project, Job, Workflow, or Dataflow) to ensure removal of any stale components in the project definition.
  2. Export the added ETL components:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select ETL.
    5. Select the deleted component's parent – Project, Job, Workflow, or Dataflow.
    6. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating a renamed ETL Project (custom)

Lower environment:

  1. After renaming the custom ETL project in SAP Data Services, ensure that both the renamed (updated) project and its previous version are synced to avoid inconsistencies or errors during synchronization.
  2. Export the added ETL components:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select ETL.
    5. Select both objects with old and new names.
    6. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating renamed ETL Component – Project, Job, Workflow, Dataflow (custom and default)

Lower environment:

  1. After renaming the ETL Component in SAP Data Services, ensure that both the renamed (updated) component and its previous version are synced to avoid inconsistencies or errors during synchronization.
  2. Export the added ETL components:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select ETL.
    5. Select both objects with old and new names.
    6. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Migrating renamed ETL Component - Loop, Catch, Try, Conditional, or Script under the parent ETL Component – Job, Workflow or Dataflow (custom and default)

Lower environment:

  1. After renaming, select the parent ETL Component - Job, Workflow or Dataflow and sync to the data source.
  2. Export the added ETL components:
    1. Go to Data Source or Staging Area.
    2. Select Export.
    3. Set Type to Custom.
    4. Select ETL.
    5. Select both objects with old and new names.
    6. Select Export.

Higher environment:

  1. Go to Data Source or Staging Area.
  2. Select Create.
  3. Set Type to Custom.
  4. Upload the exported file.
  5. Select Import.

Unsupported Scenarios

Deleting a template ETL Project from data source (default)

A default ETL project (project that is part of the imported template) cannot be deleted from the data source using the sync option and therefore cannot be migrated.

A default ETL project (project that is part of the imported template) that has been deleted from the SAP Data Services repository will not be visible in the default sync screen and cannot be deleted from the data source using the sync option and therefore cannot be migrated.

Renaming a template ETL Project (default)

A default ETL project (project that is part of the imported template) that has been renamed in the database directly cannot be synced to the data source.

Was this article helpful?

We're sorry to hear that.