Your studio offers you the possibility to store individual reports in databases different from the default report database or context connection defined in the [Preferences] window of the studio as outlined in Setting up a distant database.
Prerequisite(s): You have selected the Profiling perspective in the studio.
To configure a database connection for the current report, do the following:
In the DQ Repository tree view, expand Reports and double-click the report you want to open.
If you have already defined a default report datamart or a context connection in the studio [Preferences] window as outlined in Setting up a distant database, the connection settings are pre-filled with the values of the default datamart or context variables.
To set a context datamart connection: click the button in the Contexts view and select the context variables from the studio Repository.
For further information, see Using context variables to connect to the report database.
To set a datamart connection:
From the DB Type list, select the database in which you want to store the current report results.
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, use the same database name that is defined when installing the data quality portal from which you want to access the report results. For further information, see the 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.
When using the IPV6 address format for a local MySQL, configure the database connection using the logical hostname, localhost, and map this in the hosts file to the IPV6 local address, [::1]. Otherwise the startup of the Portal fails.
Fill the SID, the Service Name or the OCI Service Name field 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 the Talend Installation Guide.
Click Check to see the status of your connection.
A message prompts you to accept creating the database (catalog) if it does not exist.
If the version of the database you define in the report editor is older than that of the studio, a message prompts you to upgrade it. For further information, see Migrating the distant database.
Click OK to close the message.
A confirmation message is displayed.
Click OK to close the confirmation message.
Click the save icon on the report editor toolbar to save the database settings.
Run the current report.
The report will be written to the defined database.
You can always run the current report even if your new database connection is not successful. In such a case, the report will be written to the database defined in the studio [Preferences] window.