Preflight checks for Snowflake

✦TL;DR

Before [running the Snowflake crawler](/apps/connectors/data-warehouses/snowflake/how-tos/crawl-snowflake), you can run [preflight checks](/product/conne.

||

Your AI can read this via Docs MCPcurl -fsSL "https://docs.atlan.com/install-docs-mcp" | bashConnect

Before running the Snowflake crawler, you can run preflight checks to perform the necessary technical validations. The following preflight checks are completed:

Database and schema check

Information schema

✅ Check successful

❌ Check failed for $missingObjectName

Account usage

✅ Check successful

❌ Check failed for $missingObjectName

Warehouse access

✅ Check successful

❌ Operation cannot be performed / User is not authorized to perform this action / Cannot be resumed because resource monitor has exceeded its quota

Miner

Did you know?

Once you have crawled assets from Snowflake, you can mine query history.

Query history view

✅ Check successful

❌ Cannot access query history table. Please run the command in your Snowflake instance: GRANT IMPORTED PRIVILEGES ON DATABASE snowflake TO ROLE atlan_user_role;

To resolve this, see Grant Snowflake permissions for both options:

• Grant IMPORTED PRIVILEGES on the entire SNOWFLAKE database (requires ACCOUNTADMIN).
• Grant the least-privilege database roles: SNOWFLAKE.OBJECT_VIEWER, SNOWFLAKE.GOVERNANCE_VIEWER, and SNOWFLAKE.SECURITY_VIEWER.

Access history view

✅ Check successful

❌ Check failed. Something went wrong with your request.

Sessions view

✅ Check successful

❌ Check failed. Something went wrong with your request.

S3

✅ Check successful if the bucket, region, and prefix combination is valid and the S3 credential passed is accessible.

❌Check failed with error code <AWS error code> - <AWS SDK ERR message>

For example: Miner S3 credentials: failed with error code: NoSuchBucket