Import Databases
  • 25 Mar 2024
  • 2 Minutes to read
  • Contributors
  • Dark
    Light
  • PDF

Import Databases

  • Dark
    Light
  • PDF

Article summary

This topic is related to the following sections:

About Import Databases

Import Databases provides a list of the current Working Databases that are created within Syniti Knowledge Platform as connections and these working databases are then linked to a Development Area and Environment within Syniti Migrate. The Development Area is linked within the Project Setup to store the Subject Area, Working Database, and Working Datastore for the Project and Release. An example of a working database is WRKFIN, WRKOTC, or WRKMATERIAL.

Note

Where the source is SQL Server for these working databases, the datasource schema defaults automatically to dbo.

View the following page by navigating to Administer > Setup > Import Databases from the Syniti Migrate Home page or access by using the Guided Setup. The list of rows on this page contains Working Datasources created in the working dabase that have been linked to a Development Area and Environment. The system automatically attempts to link these together as part of the Guided Setup wizard should the naming be same.

null
Import Databases

The Import Databases grid displays the following:

Heading

Definition

Name

The name of the Working Database.

Development Area

The Development Area that this working database is assigned.

Environment

The Environment this working database is assigned.

Prerequisites

As defined within section Initial Setup of Supporting Database and Systems for a Working Migrate System, the databases, servers, tenants, and connections must all be setup prior to setup of this Syniti Migrate system.

Users & Roles for Guided Setup

The IT Lead or Admin is responsible for initial setup of the Syniti Migrate system. This section is stored within Administer and only users granted Admin access maintains the setting up of this process.

Add an Imported Working Database

As additional working databases become required to process and store migration conversion data, assigning these new working database to the Development Area and Environment is a necessary step in the setup process.

Note

The Working Database must have previously been created in the working database as this is the assignment portion.

  1. Click the Add icon within the header bar to select from a list of available databases.

  2. Click the Selected for Import toggle to mark the value to import.

  3. Enter values for the required fields of the selected database.

  4. If the required fields are filled, the Save icon displays to save this action.

The Import Databases grid displays the following:

Heading

Definition

Selected for Import

Toggle to select the database for use.

Database

The working database name.

Development Area*

The Development Area that this working database is assigned. (Required)

Environment*

The Environment this working database is assigned. (Required)

When working within the ETL section of Mappings, the user can now assign the new working database as an ETL Version Selection. The ETL conversion can run within multiple ETL versions.

Edit a Working Database

  1. Click the Edit icon to open the details for the selected working database.

  2. Make the necessary changes

  3. Click the Save icon to store the updates.

null
Import Database: Edit details

Remove an Imported Working Database

Click the Delete icon for the selected database to remove it from the assignment for Environments.

null
Import Database: Delete a working database assignment

Should the working database have assignment to ETL Tasks, it cannot be deleted.


Was this article helpful?

ESC

Eddy, a generative AI, facilitating knowledge discovery through conversational intelligence