Vantage integrates with your Snowflake account through a secure, read-only user that has access to Snowflake usage tables. Optionally, you can create a specific schema for the Vantage user. Vantage requires read-only access to the following tables:
NOTEAs a best practice, it is suggested you create a schema specifically for the vantage user. Note, however, that this is optional. See the steps below for details on how to create this schema.

​
Connect Your Snowflake Account

​
Prerequisites

Create a free Vantage account, then follow the steps below to integrate Snowflake costs.

​
Snowflake IP Allowed List

If your Snowflake cluster uses an IP allow list for access control, you will need to add the following IPs to that allowed list: 
54.87.66.45
3.95.43.133
54.162.3.72
44.199.143.63
3.218.103.23

​
Snowflake Schema for Vantage

After creating the below schema, you can add the required views to that schema and grant the vantage user access to the schema.
INFOThe below commands are based on the Snowflake documentation.
1

From the top navigation in Vantage, click Settings.
2

On the left navigation, select Integrations and select Snowflake.
3

The Snowflake integrations page is displayed. Ensure you are on the Connect tab.
4

Copy the code that’s provided under Create Vantage User and Role to Snowflake. This SQL creates a user named vantage, a role named vantage, and a warehouse named vantage. It also grants the necessary permissions.
NOTEVantage automatically generates an RSA public key for you to use when creating the Vantage user and role. You need to copy the code directly from the Vantage integration page to add the RSA key.
Sample of code. Copy directly from Vantage console to get RSA key.
USE role accountadmin;
CREATE DATABASE vantage;
CREATE ROLE vantage;
CREATE USER vantage;
GRANT ROLE vantage to user vantage;
GRANT ROLE vantage to role accountadmin;
CREATE WAREHOUSE vantage;
GRANT ALL ON WAREHOUSE vantage TO ROLE vantage;
ALTER USER vantage SET DEFAULT_WAREHOUSE=vantage, DEFAULT_ROLE=vantage;
ALTER USER vantage SET password='';
ALTER USER vantage SET RSA_PUBLIC_KEY='<YOUR_RSA_KEY_GENERATED_BY_VANTAGE>';
5

Copy the next code block to set up the Vantage-specific schema to read billing and usage data from your account.
USE WAREHOUSE vantage;
CREATE VIEW VANTAGE.PUBLIC.QUERY_HISTORY as select * from SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY;
CREATE VIEW VANTAGE.PUBLIC.WAREHOUSE_METERING_HISTORY as select * from SNOWFLAKE.ORGANIZATION_USAGE.WAREHOUSE_METERING_HISTORY;
CREATE VIEW VANTAGE.PUBLIC.USAGE_IN_CURRENCY_DAILY as select * from SNOWFLAKE.ORGANIZATION_USAGE.USAGE_IN_CURRENCY_DAILY;
GRANT USAGE ON SCHEMA vantage.public TO ROLE vantage;
GRANT USAGE ON DATABASE vantage TO ROLE vantage;
GRANT SELECT ON ALL VIEWS IN SCHEMA vantage.public TO ROLE vantage;
6

Test your setup in Snowflake.
USE role vantage;
SELECT * FROM vantage.public.query_history LIMIT 1;
7

At the bottom of the Vantage console Snowflake integration page, click Add Connection.
8

Add the following information to the form:
  • Server URL: In the format <account_identifier>.<region>.snowflakecomputing.com.
  • Database: The name of the database the usage views are in (e.g., vantage).
  • Schema: The name of the schema the usage views are in (e.g., public).
  • Username set for the vantage user.
9

Click Connect Account.
Costs will be ingested and processed as soon as you add the integration, but it may take several hours to populate within Vantage depending on the query volume of your warehouse. As soon as they are processed, they will be available on your All Resources Cost Report. If you decide to remove your Snowflake integration from Vantage, all costs associated with your Snowflake integration will be removed from the Vantage console.

​
Next Steps - Manage Workspace Access

Once your costs are imported, select which workspaces this integration is associated with. See the Workspaces documentation for information.

​
Data Refresh

See the provider data refresh documentation for information on when data for each provider refreshes in Vantage.

​
Troubleshoot Snowflake Errors

Snowflake occasionally makes changes to the queries/tables that get used for cost and usage attribution, causing the views in Vantage to then be based on an old query. You may see an error in the Vantage console, similar to the below error: 
View definition for 'VANTAGE.PUBLIC.QUERY_HISTORY' declared 66 column(s), but view query produces 77 column(s).
To fix the issue, replace the three Vantage views in Snowflake and ensure the vantage user is granted permission on those views.
NOTEAfter you’ve completed the below steps, contact support@vantage.sh to reimport your Snowflake data.
USE WAREHOUSE vantage;
CREATE OR REPLACE VIEW VANTAGE.PUBLIC.QUERY_HISTORY as select * from SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY;
CREATE OR REPLACE VIEW VANTAGE.PUBLIC.WAREHOUSE_METERING_HISTORY as select * from SNOWFLAKE.ORGANIZATION_USAGE.WAREHOUSE_METERING_HISTORY;
CREATE OR REPLACE VIEW VANTAGE.PUBLIC.USAGE_IN_CURRENCY_DAILY as select * from SNOWFLAKE.ORGANIZATION_USAGE.USAGE_IN_CURRENCY_DAILY;
GRANT USAGE ON SCHEMA vantage.public TO ROLE vantage;
GRANT USAGE ON DATABASE vantage TO ROLE vantage;
GRANT SELECT ON ALL VIEWS IN SCHEMA vantage.public TO ROLE vantage;

​
Snowflake Reporting Dimensions

On Snowflake Cost Reports, you can filter across several dimensions:
  • Account (account name)
  • Category (e.g., Data Cloud Data Transfer)
  • Metadata (e.g., environment is staging)
  • Region (e.g., AWS Eu West 1)
  • Organization (organization name)
  • Service (e.g., Data Cloud)
  • Tag
  • Charge Type (e.g., Usage)

​
Active Resources

Snowflake queries are synced as active resources and available in resource reports.