By default, your studio stores reports and analyses in an embedded HSQL database. Usually, you will want to set up a distant database accessible by other users and thus share the results of the analyses and further exploit them via Talend Data Quality Portal.
From the Profiling perspective of the studio, you can set up a distant database, MySQL or Oracle for the time being. This database will be the by-default distant database that stores all reports and analysis results unless you decide to store individual reports in a database different from this one. For further information, see Setting up a database for an individual report.
For further information about the Portal, see the Talend Data Quality Portal User and Administrator Guide. For further information on installing Talend Data Quality Portal, see Talend Installation Guide.
Prerequisite(s): You have selected the Profiling perspective in the studio.
To set up a distant database, do the following:
In the menu bar, select Window > Preferences to display the [Preferences] window.
Start typing Reporting in the filter field and then select Reporting from the list to open the [Reporting] page.
In the DB Type list, select the name of the database you want to define.
By default, your studio stores reports and analysis results in an embedded HSQL database. You can not share reports and analysis results when stored in the HSQL database.
Define the connection parameters in the individual connection fields or directly in the Url field.
When you modify any parameter in the Url field, it is modified automatically in the individual fields and vice versa.
In the DB Name, you must use the same database name that is defined when installing Talend Data Quality Portal. For further information, see Talend Installation Guide.
In the DB Name field, you can either:
enter a database name (catalog) that does not exist in your database. The studio will create a new catalog and generate all the required tables to store your analyses and reports, or,
use the by-default database name (talend_dq). In this database, you can have access to all analyses and results of generated reports.
Fill the SID, the Service Name or the OCI Service Namefield with the name of an existing database.
Fill the Schema field with an Oracle schema to which the specified user in the User field has access, or leave it blank. If you leave this field blank, your reports will be written to the default schema of the defined user.
For PostgreSQL or SQL Server, fill in the connection information to the database. You can use only the default schemas of PostgreSQL or SQL Server when you create the datamart on them.
To enable writing reports to the defined database, make sure that the specified user has enough system privileges. For further information, see Talend Installation Guide.
Enter your login information to the database in the corresponding fields.
If needed, click Export as context and follow the steps in the wizard to export the datamart connection and the path of the report folder and logo as a context.
For further information, see Using context variables to connect to the report database.
You can click Revert Context to switch the connection back to its initial state.
Click Apply to report editors... to open a list from which you can select the reports which results you want to store in the defined datamart or context connection. For further information, see Migrating the database for a group of reports.
Click Apply to store the results of all analyses and reports in the defined database.
Click OK to validate the changes and close the [Preferences] window.
When the version of the distant database created from the Profiling perspective of the studio is older than that of the studio, a pop-up message is displayed to ask you if you want a database upgrade. For more information, see Migrating the distant database.
In case of a database connection failure, a check-connection dialog box is displayed to give a tip on possible reasons of the connection failure.