Reader account users cannot add new data to the account.

Reader account users can share data to other reader accounts.

A single reader account can consume data from multiple provider accounts.

Data consumers are responsible for reader account setup and data usage costs.

Reader accounts enable data consumers to access and query data shared by the
provider.

CREATE_SHARE on the account

SHARE on databases and schemas

SELECT on tables used by the secure view

REFERENCE_USAGE on databases

Row level access policies

Data masking policies

Data encryption

Time Travel

External tokenization

The database ACCOUNTADMIN must define the clustering methodology for each
Snowflake table

Clustering is the way data is grouped together and stored within Snowflake micropartitions.

The clustering key must be included in the COPY command when loading data into Snowflake.

Clustering can be disabled within a Snowflake account.

Caching query results

Running EXPLAIN and SHOW commands

Cloning a database

Running a custom query

Running COPY commands

There is no Fail-safe period for these tables.

1 day

7 days

31 days

90 days

Possibly, if the warehouse is resized to a smaller size and the cache no longer fits.

Yes. because the compute resource is replaced in its entirety with a new compute resource.

No. because the size of the cache is independent from the warehouse size

Yes. became the new compute resource will no longer have access to the cache encryption key

Snowflake will resolve them according to the SEARCH_PATH parameter.

Snowflake will only check the schema the UDF belongs to.

Snowflake will first check the current schema, and then the schema the previous query used

Snowflake will first check the current schema, and them the PUBLIC schema of the
current database.