Setting up a distant database - Cloud - 8.0

Talend Studio User Guide
Version
Cloud
8.0
Language
English
Product
Talend Big Data
Talend Big Data Platform
Talend Cloud
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Design and Development
Last publication date
2023-11-24
Available in...

Big Data Platform

Cloud API Services Platform

Cloud Big Data Platform

Cloud Data Fabric

Cloud Data Management Platform

Data Fabric

Data Management Platform

Data Services Platform

MDM Platform

Real-Time Big Data Platform

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

From the Profiling perspective, 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.

Procedure

  1. On the menu bar, click Window > Preferences.
  2. In the Preferences window, do one of the following:
    • Start typing reporting and select Reporting.
    • Expand Talend > Profiling and select Reporting.
  3. From the DB Type list, select the database in which you want to store the current report results.
    By default, Talend 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 in the Url field. When you modify any parameter in the Url field, it is modified automatically in the individual fields and vice versa.
    Database Details
    MySQL In the DB Name field, you can:
    • Enter a new database name (catalog). A catalog will be created and the required tables to store analyses and reports will be generated.
    • Use the default database name (talend_dq). In this database, you can have access to all analyses and results of generated reports.
    • Enter a 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 in a lower version that the current one, the data mart structure is updated.

      If the data mart structure already exists but in an higher version that the current one, you cannot use this data mart structure.
      Remember: MySQL database names with a dot "." are allowed.
      You can connect to an Azure Database for MySQL.
    Oracle with SID

    Oracle with service name

    Oracle OCI
    • Fill the SID or the 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.
    Important: The collation of the schema must be case sensitive. Otherwise the columns may not be analyzed and will be missing from the report. For more information, see the Oracle documentation.
    PostgreSQL
    • Fill in the connection information to the database.
      Remember: Database names with a dot "." or an hyphen "-" are allowed.
    • You can connect to an Azure Database for PostgreSQL or an Azure SQL database. When connecting to an Azure Database for PostgreSQL database, use the username@hostname syntax for the User field and leave the Additional parameters field empty.
    • You can use only the default schemas of PostgreSQL when you create the data mart on it.
    Microsoft SQL Server
    • Fill in the connection information to the database.
      Remember: Database names with a dot "." or an hyphen "-" are allowed.

      To enable writing reports to the defined database, make sure that the specified user has enough system privileges.

    • You can use only the default schemas of Microsoft SQL Server when you create the data mart on it.
    • If you want to connect using 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 and Open source JTDS drivers are supported.

    • The collation used by the Microsoft SQL Server database must be case-insensitive, otherwise the report generation may not succeed. You may encounter the following error: java.sql.SQLException: Invalid column name 'rep_runtime'. For more information about collation rules, see Microsoft documentation.
    • For more information about setting up a connection to a Microsoft SQL Server database, see What you need to know about some databases.
  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 properties. 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. Optional: To export the data mart connection and the path of the report folder and logo as a context, click Export as context and follow the steps.
    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 data mart 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.