Skip to main content Skip to complementary content

Setting up a distant database

Availability-noteDeprecated
Talend DQ Portal is deprecated from Talend 7.1 onwards.

By default, Talend Studio stores reports and analyses in an embedded HSQL database.

From the Profiling perspective Talend Studio, you can set up an other default distant database to store reports and analysis results. You will then be able to share the results of the analyses with other users and further exploit those results via Talend DQ Portal .

Before you begin

You have selected the Profiling perspective of Talend Studio.

Procedure

  1. In the menu bar, select Window > Preferences to display the Preferences window.
  2. Start typing Reporting in the filter field and then select Reporting from the list to open the Reporting page.
  3. 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 cannot share reports and analysis results when stored in the HSQL database.
  4. 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 DQ Portal.
    For MySQL:
    In the DB Name field, you can:
    • 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
    • use the default database name (talend_dq). In this database, you can have access to all analyses and results of generated reports,
    • enter a new database name that exists in the database. If there is no data mart structure in this database, it will be created. If the data mart structure already exists but is a lower version that the current one, the data mart structure is updated. If the data mart structure already exists but is an higher version that the current one, you cannot use this data mart structure.
    MySQL database names with a dot "." are allowed.
    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.
    You can connect to an Azure forMySQL database.
    For Oracle:
    • 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 Microsoft SQL Server, fill in the connection information to the database. You can use only the default schemas of PostgreSQL or Microsoft SQL Server when you create the datamart on them.
    PostgreSQL and Microsoft SQL Server database names with a dot "." or an hyphen "-" are allowed.
    You can connect to an Azure for PostgreSQL or an Azure SQL database.
    When connecting to an Azure for PostgreSQL database, use the username@hostname syntax for the username and leave the Additional parameters field empty.
    For Microsoft SQL Server, If you want to connect through Windows authentication, leave the User and Password fields empty.
    When creating a connection to a Microsoft SQL Server database to store reports and analysis results, both Microsoft JDBC and JTDS open source drivers are supported.
    For more information about setting up a connection to a Microsoft SQL Server database, see What you need to know about some databases.
    Information noteWarning: To enable writing reports to the defined database, make sure that the specified user has enough system privileges.
  5. If you have not selected HSQL from the DB Type list, specify additional connection properties in the Additional parameters field.
    When connecting to a MySQL 8 database, configure the useSSL, requireSSL and serverTimezone property. Enter useSSL=false&requireSSL=false&serverTimezone=UTC for example.
    When connecting to an Azure SQL database, enter ssl=require.
  6. Enter your login information to the database in the corresponding fields.
  7. 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.
  8. Either:
    • 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.
    • Click Apply to store the results of all analyses and reports in the defined database.
  9. Click OK to validate the changes and close the Preferences window.
    When the version of the distant database created from the Profiling perspective of Talend Studio is older than that of the Talend Studio, a pop-up message is displayed to ask you if you want a database upgrade.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here