Database privileges for Talend Data Quality Portal

Talend Data Management Platform Installation Guide for Linux

EnrichVersion
6.2
EnrichProdName
Talend Data Management Platform
task
Installation and Upgrade

When you use Talend Installer to install Talend Data Quality Portal, you can select a specific database to store analysis results. For further information about supported databases, see Compatible Databases.

Prerequisites

If you select to use the MySQL, PostgreSQL or SQL server database to store the analysis results, the database is created automatically by the installer. However, when you select to use the Oracle database you must create the database and the schema before installing the Portal via Talend Installer.

When defining the database to store analysis results, you must:

  • make sure that users of the Portal are granted the right privileges on different databases as described in Privileges in databases.

  • make sure, for the PostgreSQL database, to add the IP of the computer which will install the Portal on the PostgreSQL server.

Privileges in databases

To enable users to write analysis results to any of the supported databases, you must grant them certain system privileges.

What privileges are necessary for Mysql

The user you define when you configure the report datamart connection must have certain privileges. Use grant commands to give at least the following system privileges:

  • Select.

  • Insert.

  • Update.

  • Create.

  • Drop.

  • Index.

  • Alter.

  • Create View.

SQL statement: GRANT <privilege> ON`<database_name>`.* TO <user_name>@'%' identified by <user_password>.

What privileges are necessary for Oracle

The user you define when you configure the report datamart connection must have either the DBA role, or the CONNECT and RESOURCE roles. Use grant commands to give the user system privileges as the following:

The privileges required when creating a datamart within the user's own schema are:

  • create a sequence.

  • create session.

  • create alter session.

  • create table.

  • create view.

An example of an SQL statement could be: GRANT create session to <user>.

The privileges required when creating a datamart within a schema which is not owned by the current user are:

  • alter any table.

  • comment any table.

  • create any index.

  • create any sequence.

  • create any table.

  • create any view.

  • create session.

  • insert any table.

  • select any sequence.

  • select any table.

  • update any table.

An example of an SQL statement could be: GRANT alter any table to <user_name>.

What privileges are necessary for PostgreSQL

The user you define when you configure the report datamart connection must either have the DBA role (like the postgres user), or at least has necessary privileges as the following:

  • CREATE USER <user_name> WITH PASSWORD <user_password>.

  • CREATE DATABASE <database_name>.

  • GRANT ALL PRIVILEGES ON DATABASE <database_name> to <user_name>.

Note

If you want to use the PostgreSQL database with the Portal, you must add the IP of the computer which will install the Portal on the PostgreSQL server.

Only the default schema, public, is used for now.

What privileges are necessary for SQL server

The user you define when you configure the report datamart connection must either have the DBA role (like the sa user), or you can use SQL commands to create a user and a database as the following:

Create database <database_name>.

Create login:

  • CREATE LOGIN <user_name> WITH PASSWORD = <user_password>.

Grant <user_name> the db_owner role in <database_name>.

  • USE <database_name>.

  • ALTER LOGIN <user_name> with default_database = <database_name>.

  • CREATE USER <user_name> FROM LOGIN <user_name>.

  • EXEC sp_addrolemember db_owner, <user_name>.

Only the default schema, dbo is used for now.