Skip to main content
Skip table of contents

Databases Management

The Databases management page contains a listing of the uploaded sources and allows:

  • Uploading new sources.

  • Configuring feature settings.

  • Performing various actions on the uploaded sources and their features.

Databases listing.png

The Databases management page

Actions Panel

The Actions panel contains key actions that can be performed on database sources.

Actions panel 1.png

The Actions panel

Available actions:

Actions Exclude.png

Exclude the selected sources from the migration analysis.

Actions Include.png

Include the selected sources in the migration analysis.

Actions Delete.png

Delete the selected sources from mConsole.

Actions Download.png

Download the selected sources to save them locally in an encrypted format.

Actions Export.png

Export the technical reports for the selected sources.

Actions Source Tags.png

Apply tags to sources for categorization, organization, and filtering purposes.

General Settings

The Databases Settings page allows choosing features to consider during the analysis.

Actions panel 2.png

The Settings icon

The Features section displays features of all sources uploaded to mConsole. By default, migVisor uses all detected features to calculate migration complexity.

The Status column shows the current feature inclusion configuration:

  • Included – the feature is included in the analysis for all databases.

  • Excluded – the feature is excluded from the analysis for all databases.

  • Partial – the feature is excluded from the analysis for at least one database.

Managing Features

To include in or exclude from the analysis a feature applicable to all databases:

  1. On the Databases Settings page, turn the corresponding feature toggle on or off in the Status column.

  2. Press the Save button.

    General Settings.png

To include in or exclude from the analysis a feature applicable to specific databases:

  1. On the Databases Settings page, press the corresponding feature configuration icon.

    Configuration icon.png
  2. Turn the corresponding database toggle on or off in the Status column.

  3. Press the Save button.

    General Settings, Feature.png

To reset all settings, press the “three dots” icon in the upper-right corner and press Reset settings.

Filter and Search

Use the Filter functionality to:

  • Search by database name or its part.

  • Filter by DB engine, version, topology, source inclusion, feature inclusion, and tags.

  • Sort the list alphabetically (ascending, descending order) using the sort icon next to the column name.

Uploaded Sources

Each uploaded source is presented as a separate row and contains the following information:

  • Source identity. For more details, see Catalog | Catalog-Item-Header.

  • Database engine and its version.

  • Associated applications.

  • Schema inclusion.

  • Feature inclusion.

  • Status.

Additional Details

The Additional Details pane is DB-engine-specific and contains metadata collected for the source in terms of identity, resources, and metrics.

To expand or collapse the Additional Details pane of:

  • A particular source, press the chevron icon in the row.

  • All listed or filtered sources, press the expand icon in the header.

Additional Details pane DB.png

The Additional Details pane of a PostgreSQL database

Database Settings

The Single Database Settings page provides options to:

  • Configure source details.

  • Include or exclude source features and schemas.

Single DB Settings.png

The Database Settings icon

The database settings content is source-specific:

DB2 LUW
  • Features

  • Schemas

HBase
  • Features

MongoDB
  • Features

  • Databases

MySQL
  • Configurable details

  • Features

Oracle
  • Configurable details

  • Features

  • Schemas

PostgreSQL
  • Configurable details

  • Features

  • Schemas

SQL Server
  • Features

Feature and Schema Statuses

In the Features section, feature statuses can be:

  • Included – default. The feature is included for the database and for some or all of the database's included schemas.

  • Included (Unused) – the feature is included for the database but for none of the database's included schemas.

  • Excluded – the feature is excluded for the database.

In the Schemas section, schema statuses can be:

  • Included – default. The schema is included for the database with all of its features.

  • Included (Partial) – the schema is included for the database with some of its features.

  • Included (Unused) – the schema is included for the database without any of its features.

  • Excluded – the schema is excluded for the database.

When all schemas are excluded in a particular database, this database is not excluded but is presented with a zero scoring without any features in it.

When all schemas that a certain feature belongs to are excluded, this feature is also excluded from the migration analysis.

The exclusion of schemas or features affects the complexity score.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.