Setting up a database for an individual report

You can store individual reports in databases other than the default report database.

1. 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, the connection settings are pre-filled with the values of the default datamart or context variables.
2. To set a context datamart connection, click the button in the Contexts view and select the context variables from the Talend Studio Repository.
3. 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 from which you want to access the report results.
   For MySQL:
   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
   • 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.

   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 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 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.

   Information noteWarning: To enable writing reports to the defined database, make sure that the specified user has enough system privileges.
4. 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.
5. 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.
6. Click OK to close the message.
   A confirmation message is displayed.
7. Click OK to close the confirmation message.
8. Click the save icon on the report editor toolbar to save the database settings.
9. Run the current report.
   The report will be written to the defined database.
   If the connection to the new database connection is not successful, the report will be written to the database defined in the Preferences window.