1. DB Best Documentation
  2. Schema conversion

Schema conversion

The schema conversion module accesses an external conversion tool and displays the conversion results on UI. Thus, in the Schema conversion window, you can see how the target tree structure will look as a result of the conversion.

Note: The module doesn’t record the displayed results. To keep the results, you have to Apply them to a database or Save as SQL by selecting the corresponding options in the context menu.

Schema conversion list

Figure 1. Selecting data for conversion

DB Best Migration Platform provides for three external conversion tools:

To specify the external conversion tool go to  Global Settings —> External Tools and set the required configuration (Figure 1).

Migration Platform external tools

Figure 2. Available external tools

Running the Assessment Report

Schema conversion module allows for creating an assessment report, which retrieves the number of sources objects that the system converts automatically.

To run the assessment report:

  1. Check the required objects in the Source metadata tree
  2. Click the Run Assessment Report button (Figure 3)
Assessment report selection

Figure 3. Running an assessment report

Depending on the external conversion tool you selected (as described above), the platform returns results as:

  • PDF file — for AWS SCT, or
  • HTML file — for SSMA

The conversion tool also defines what console (AWS SCT or SSMA) the Schema conversion module leverages. This impacts the difference in commands you can encounter in scripts.xml generated by the module.

For SCT:

  • SetProjectSetting — sets up the drivers for database connection
  • NewProjectCommand — creates a new conversion project
  • ConnectCommand — connects to the source/target database vendor
  • LoadTreeNodeCommand — loads metadata object from the database
  • TransformTreeNodeCommand — converts the selected metadata objects
  • ReportToPdfFileCommand — saves the results of conversion

For SSMA:

  • create-new-project — creates a new conversion project
  • connect-source-database — connects to the source database vendors
  • generate-assessment-report — starts conversion and generates output into an HTML report

Converting schema

The Convert schema operation shows the objects in the Target metadata tree that the system intends to write to the target database.

Depending on the user’s preferences, it can either be a new or an existing project.

To convert a schema:

  1. Check the required schemas in the Source and Target metadata trees
  2. Click the Convert Schema button
  3. Once selected, the Convert schema button will offer to choose between converting schema for a new project (Convert schema with SCT/SSMA/Ora2Pg) or for an existing project (Convert schema using project SCT/SSMA/Ora2Pg). A new project will require a correct path to the console file in Global settings, meanwhile, an existing project can be selected from the previously saved migration reports.
Schema conversion

Figure 4. Choosing between new and existing projects

If you want to convert schema using a new project, Migration Platform will automatically redirect you to Settings (as shown in Figure 2). Choosing the existing project option will automatically open the browsing window for the migration reports folder.

Existing project

Figure 5. Specifying the route to existing projects

After the process is over, the converted objects will be highlighted in bold in the Target metadata tree.

To keep the results, in the context menu of the Target metadata tree, select the Apply to database or Save as SQL option.

Figure 6. Applying conversion results to the database

Schema mapping

You can specify schema mapping mode for the Schema conversion. To do so, go to the project settings and select the mapping mode (Figure 4):

  1. SchemaToSchema (default)
  2. SchemaToDatabase
  3. Custom mapping — when you start schema conversion, you see the window to enter the names of the target database and schema
Figure 3. Schema Conversion settings for SSMA

Figure 7. Schema conversion settings

Schema conversion module generates the script that contains the following commands:

For SSMA:

  1. create-new-project — creates a new conversion project
  2. connect-source-database — connects to source database vendors
  3. connect-target-database — connects to target database vendors
  4. map-schema — sets mapping between the source and target schemas
  5. convert-schema — converts the selected metadata objects

For SCT:

  1. SetProjectSetting — sets up drivers for database connection
  2. NewProjectCommand — creates a new conversion project
  3. ConnectCommand — connects to the source/target database vendor
  4. LoadTreeNodeCommand — loads metadata object from the database
  5. TransformTreeNodeCommand — converts selected metadata objects
  6. ReportToCSVFileCOmmand — saves the results of the conversion operation

Didn’t find the answer?

You can report problems, ask questions or share ideas for improvements on our email [email protected].