1 of 7

Query Data

Querying Snowflake Data

Prerequisites:

Query data with Snowflake table grants

Execute the USE SECONDARY ROLES ALL command or change your role to the table grants role.
Query the data as you normally would in Snowflake.
```
SELECT * FROM emp_basic LIMIT 100;
```

Query data without Snowflake table grants

Prerequisite: Users have been granted SELECT privileges on all or relevant Snowflake tables

Query the data as you normally would in Snowflake:

SELECT * FROM emp_basic LIMIT 100;

Querying Databricks Data

Prerequisites:

Query data with Python

Create a new workspace.

Query the Immuta-protected data as you normally would:

df = spark.sql('select * from database.table_name')
df.show()

Query data with SQL

Create a new workspace.
Query the Immuta-protected data as you normally would:
```
select * from database.table_name;
```

Querying Starburst (Trino) Data

Prerequisites:

Query data

Use your tool of choice to connect to Starburst.
Query the Immuta-protected data as you normally would:
```
select * from "tpch"."sf1000"."customer" limit 100
```

Querying Databricks SQL Data

Prerequisites:

Query data

Select SQL from the navigation menu in Databricks.
Click Create → Query.

Run your query as you normally would:

SELECT
  concat(pickup_zip, '-', dropoff_zip) as route,
  AVG(fare_amount) as average_fare
FROM
  `samples`.`nyctaxi`.`trips`
GROUP BY
  1
ORDER BY
  2 DESC
LIMIT 1000

Querying Redshift Data

Prerequisites:

Redshift integration configured with Immuta
Redshift tables registered as Immuta data sources
REVOKE users' access to raw tables

Query data

Use your tool of choice to connect to Redshift.
Select the Immuta database name used when configuring the integration.
Query the Immuta-protected data, which takes the form of immuta_database.backing_schema.table_name:
1. Immuta Database: The Immuta database name used when configuring the integration.
2. Backing Schema: The schema that houses the backing tables of your Immuta data sources.
3. Table Name: The name of the table backing your Immuta data sources.
Run your query (it is recommended that you use the catalog in the query). It should look something like this:
```
select * from immuta_database.backing_schema.table_name limit 100
```

Querying Azure Synapse Analytics Data

Prerequisites:

REVOKE users' access to raw tables
GRANT users' access to the Immuta schema

Query data

Click the Data menu in Synapse Studio.
Click the Workspace tab.
Expand the databases, and you should see the dedicated pool you specified when .
Expand the dedicated pool and you should see the Immuta schema you created when .
Select that schema.
Select New SQL script and then Empty script.
Run your query (note that Synapse does not support LIMIT and the SQL is case sensitive). It should look something like this:

Querying Redshift Data

Prerequisites:

Redshift integration configured with Immuta
Redshift tables registered as Immuta data sources
REVOKE users' access to raw tables

Query data

Use your tool of choice to connect to Redshift.
Select the Immuta database name used when configuring the integration.
Query the Immuta-protected data, which takes the form of immuta_database.backing_schema.table_name:
1. Immuta Database: The Immuta database name used when configuring the integration.
2. Backing Schema: The schema that houses the backing tables of your Immuta data sources.
3. Table Name: The name of the table backing your Immuta data sources.
Run your query (it is recommended that you use the catalog in the query). It should look something like this:
```
select * from immuta_database.backing_schema.table_name limit 100
```