Skip to content

You are viewing documentation for Immuta version 2.8.

For the latest version, view our documentation for Immuta SaaS or the latest self-hosted version.

Accessing Data via Immuta SQL Connection

Audience: Data Users

Content Summary: This page highlights the process for using the SQL connection to access data sources, projects, and third-party tools.

SQL Access to Data Sources

If you don't have a tool to connect to PostgreSQL, you can download and install pgadmin: You can use the provided connection string to configure your application to consume data through Immuta. Make sure to include your real password in the connection string as it will not be provided in the connection string by default.

Once you’ve hooked in your BI tool of choice, or installed the above tool and connected, you should see available tables in the Immuta database — these tables are the exposed Immuta data sources. All of the Immuta data sources look and feel just like PostgreSQL tables (when they are actually a proxy for the real data source). This means you can execute cross-database technology queries since to you, they are just PostgreSQL tables.

You will only be allowed to run queries on data sources you are subscribed to and against data you have appropriate authorizations to view.

SQL Access to Project Data Sources

Users who wish to query a data source using a project purpose must use project-specific SQL credentials. These special credentials will only provide access to the data sources in their respective projects and allow Data Governors to enforce purpose-based restrictions on project data.

Third-Party Tools

Many industry-standard analytic and BI tools can leverage the Immuta Query Engine to consume data. For more information, click here.