Prerequisites:
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;Prerequisite: Users have been granted SELECT privileges on all relevant Snowflake tables
Query the data as you normally would in Snowflake:
SELECT * FROM emp_basic LIMIT 100;Prerequisites:
Create a new workspace.
Query the Immuta-protected data as you normally would:
df = spark.sql('select * from database.table_name')
df.show()Create a new workspace.
Query the Immuta-protected data as you normally would:
select * from database.table_name;select * from "tpch"."sf1000"."customer" limit 100SELECT
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 1000Prerequisites:
REVOKE users' access to raw tables
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:
Immuta Database: The Immuta database name used when configuring the integration.
Backing Schema: The schema that houses the backing tables of your Immuta data sources.
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 100Prerequisites:
REVOKE users' access to raw tables
GRANT users' access to the Immuta schema
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:
SELECT TOP 100 * FROM immuta_schema.backing_database_backing_table;