Migrating the distant database - 6.2

Talend Data Management Platform Studio User Guide

EnrichVersion
6.2
EnrichProdName
Talend Data Management Platform
task
Data Quality and Preparation
Design and Development
EnrichPlatform
Talend Studio

By default, your studio stores the reports and analyses in an embedded HSQL database unless you define a distant database from the [Preferences] window of the studio as outlined in Setting up a distant database.

When you launch a brand new studio for the first time, the database settings in the [Preferences] window of the studio always refers to HSQL. If you start by defining the distant database in the new studio before importing your reports or projects from an older version, you do not need to migrate the distant database to be able to generate reports from the current studio and store them in the defined database.

However, if you import your reports or project from an older version of the studio before setting the distant database in the [Preferences] window, you must migrate the database in order to be able to generate reports and store them in the defined database as explained below in this section. The version of the distant database must always match that of the studio.

Prerequisite(s): You have already migrated your reports or your project from an older version of the studio as outlined in Importing data profiling items or projects.

To migrate the distant database from the [Preferences] window, do the following:

  1. In the menu bar, select Window > Preferences to display the [Preferences] window.

  2. Expand Talend > Profiling and then select Reporting to open the [Reporting] page.

  3. Set the distant database connection information as outlined in Setting up a distant database and click Apply.

    A warning message is displayed to prompt you to migrate the database.

    Note

    You can do a mass database upgrade only for a group of reports and not all of them if you click the Apply to report editors... button in the [Preferences] window. For further information, see Migrating the database for a group of reports

  4. Click OK to confirm the database migration and close the warning message.

    An information bar is displayed to show the progress of the operation followed by a message that confirms the database upgrade.

  5. Click OK to close the confirmation message and the [Preferences] window.

  6. In the DQ Repository tree view and under the DB Connections node, right-click the MySQL or Oracle connection you defined and select Reload database list.

    This will list the newly created database in the connection list in the DQ Repository tree view. All generated reports in the current studio will be stored in this database unless different databases are defined in the report editor for different reports.

To migrate the database for an individual report from the report editor, do the following:

  1. In the DQ Repository tree view, expand Reports and double-click the report whose database you want to migrate.

  2. At the bottom of the editor and in the Database Connection Settings view, set in the fields the settings of the database of your choice and click Check.

    If the report database version does not match that of the studio, a message prompts you to migrate the report database.

  3. Click OK to confirm the database migration and close the message.

    An information bar is displayed to show the progress of the operation followed by a message that confirms the database upgrade.

  4. Click OK to close the confirmation message.

    A new report database that matches the current studio version is created.

  5. In the DQ Repository tree view and under the DB Connections node, right-click the MySQL or Oracle connection you defined and select Reload database list.

    This will list the new report database in the connection list in the DQ Repository tree view. The generated current report will be stored in the defined database.

    Note

    If you have imported many reports in your current studio, you can do a mass database upgrade for a group of reports as this will be less time consuming. For further information, see Migrating the database for a group of reports.