# Setting up a distant database

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
* Qlik Talend Cloud Enterprise Edition
* Qlik Talend Cloud Premium Edition
* 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 another default distant database to store reports and analysis results. You will then be able to share the results of the analyses with other users.

Information noteImportant: Since Talend Studio 8.0 R2025-02, the Talend Data Quality data mart is no longer included in Talend Installer. This procedure in Talend Studio is now the primary method to configure and initialize the data mart. For information about supported databases, see [Supported databases for the data mart](https://help.qlik.com/talend/en-US/studio-user-guide/8.0-R2026-09/reports).

## 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. ![Location of Reporting in the Preferences list.](https://help.qlik.com/talend/en-US/studio-user-guide/Resources/images/preferences-reporting.png)
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:<br><br><ul> <li>Enter a new database name (catalog). A catalog will                                be created and the required tables to store analyses                                and reports will be generated.</li> <li>Use the default database name                                (<kbd>talend_dq</kbd>). In this                                database, you can have access to all analyses and                                results of generated reports.</li> <li>Enter a database name that exists in the database.                                        <p>If there is no data mart structure in this database, it will be created. </p> <p>If                                        the data mart structure already exists but in a lower                                        version that the current one, the data mart structure is                                        updated. </p>If the data mart structure already exists but                                    in an higher version that the current one, you cannot use this                                    data mart structure.<div><span>Information note</span><span>Remember:</span> MySQL database names                                        with a dot "<kbd>.</kbd>" are                                        allowed.</div>You can connect to an Azure Database for                                    MySQL.</li> </ul> |
   | Oracle with SID<br><br>Oracle with service name<br><br>Oracle<br>OCI | <ul> <li>Fill the <span>SID</span> or the                                    <span>Service Name</span> field with the                                    name of an existing database.</li> </ul><br><br><ul> <li>Fill the <span>Schema</span> field with an                                    Oracle schema to which the specified user in the                                    <span>User</span> 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. </li> </ul><br><br>Information noteImportant: The collation of the schema must be case<br>sensitive. Otherwise the columns may not be analyzed and will be<br>missing from the report. For more information, see the [Oracle documentation](https://docs.oracle.com/en/database/oracle/oracle-database/18/nlspg/linguistic-sorting-and-matching.html#GUID-2AC4EE67-D3C0-4E26-87AD-2DA4584F874A). |
   | PostgreSQL | <ul> <li>Fill in the connection information to the database.<div><span>Information note</span><span>Remember:</span> Database names with a dot                                            "<kbd>.</kbd>" or an hyphen                                            "<kbd>-</kbd>" are                                    allowed.</div> </li> <li>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                                    <kbd>username@hostname</kbd> syntax                                    for the <span>User</span> field and leave                                    the <span>Additional parameters</span>                                    field empty.</li> <li>You can use only the default schemas of PostgreSQL                                    when you create the data mart on it.</li> </ul> |
   | Microsoft SQL Server | <ul> <li>Fill in the connection information to the database.<div><span>Information note</span><span>Remember:</span> Database names with a dot                                            "<kbd>.</kbd>" or an hyphen                                            "<kbd>-</kbd>" are allowed. <p>To                                            enable writing reports to the defined database, make                                            sure that the specified user has enough system                                            privileges.</p> </div> </li> <li>You can use only the default schemas of Microsoft                                    SQL Server when you create the data mart on it.</li> <li>If you want to connect using Windows authentication, leave the                                        <span>User</span> and                                        <span>Password</span> fields empty. <p>When                                        creating a connection to a Microsoft SQL Server database to                                        store reports and analysis results, both                                            <span>Microsoft</span> and <span>Open                                            source JTDS</span> drivers are supported.</p> </li> <li>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: <span>java.sql.SQLException:                                        Invalid column name 'rep_runtime'</span>. For                                    more information about collation rules, see <a href="https://docs.microsoft.com/en-us/sql/t-sql/statements/windows-collation-name-transact-sql?view=sql-server-2017" target="_blank">Microsoft                                        documentation</a>.</li> <li>For more information about setting up a connection                                    to a Microsoft SQL Server database, see <a href="https://help.qlik.com/talend/en-US/studio-user-guide/8.0/what-you-need-to-know-about-some-databases" target="_blank">What you need to know about some databases</a>.</li> </ul> |
   | Snowflake | You need the following Snowflake privileges to run reports when<br>the data mart is on<br>Snowflake:<br><br>```<br>GRANT USAGE on WAREHOUSE <WAREHOUSE_NAME> to <ROLE_NAME><br><br>GRANT USAGE on DATABASE <DB_NAME> to <ROLE_NAME><br><br>GRANT USAGE on ALL SCHEMAS IN DATABASE <DB_NAME> to <ROLE_NAME><br><br>GRANT SELECT, INSERT, UPDATE on ALL TABLES in DATABASE <DB_NAME> to <ROLE_NAME><br><br>GRANT SELECT, INSERT, UPDATE on ALL VIEWS in DATABASE <DB_NAME> to <ROLE_NAME><br><br>GRANT USAGE on ALL SEQUENCES in DATABASE <DB_NAME> to <ROLE_NAME><br>``` |
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](https://help.qlik.com/talend/en-US/studio-user-guide/8.0/using-context-variables-to-connect-to-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.