Enable Warehouses

After deploying the Yuki Proxy and configuring security, the next step is to enable optimization for Snowflake warehouses. This allows Yuki to route queries through your proxy and apply per-query cost and performance optimization.

💡 Note: You don’t need to perform these steps manually during onboarding - Yuki’s wizard guides you through warehouse selection automatically.

1. What It Does

When you toggle a warehouse on, Yuki:

  • Registers it for optimization and routing.

  • Begins collecting query-level metrics and cost data.

Yuki does not modify any connection strings automatically - you’ll update them manually in your tools to complete activation.

2. Prerequisites

Before enabling warehouses, make sure:

  • You completed the “Grant Yuki Access to Snowflake” step.

  • The Yuki Proxy (Fully Hosted, Helm, or Terraform) is up and connected.

  • You have ACCOUNTADMIN or similar privileges in Snowflake.

3. Enable Warehouses

In this step of the onboarding wizard, you’ll see a list of all Snowflake warehouses detected in your connected account. Toggle ON the warehouses you want Yuki to optimize.

Once enabled, Yuki registers those warehouses for optimization and starts monitoring their queries in real time.

💡 Note: You can always return later to enable additional warehouses or turn optimization off at any time.

4. Switch Connection Strings

After enabling warehouses, update your connection configurations so your tools and applications route queries through the Yuki Proxy instead of directly to Snowflake. Only the hostname changes - credentials, roles, and warehouses remain the same.

4.1 Connecting with dbt

dbt Cloud

For dbt Cloud, dbt provides Extended Attributes, which let you define a profiles.yml snippet in your Environment settings. Under the Deployment Settings for your Environment, add a host parameter to the Extended Attributes. For example:

snowflake-locator.yukicomputing.com

dbt Core

For dbt Core, add a host parameter in your profiles.yml file. For example:

account: snowflake-locator.yukicomputing.com

4.2 Connecting with Looker

Looker connects to Snowflake using the JDBC driver. Override the Remote Host:Port parameter wto your Yuki Proxy hostname. For example:

snowflake-locator.yukicomputing.com:443

4.4 Connecting with Tableau

Tableau connects to Snowflake using the ODBC driver. Update the server parameter with the Yuki Proxy hostname. For example:

snowflake-locator.yukicomputing.com

Depending on your Snowflake authentication method, you may need to complete a few additional configuration steps.

Connecting with Tableau using OAuth

When using OAuth, Tableau redirects users to Snowflake for authentication before data can be queried. When connecting through Yuki, Tableau must redirect users to the Yuki Proxy hostname, for example:

https://snowflake-locator.yukicomputing.com

instead of:

snowflake-locator.snowflakecomputing.com

Make sure you’re using Tableau version 2024.2 or later, then follow the steps below based on your Tableau environment to enable custom Snowflake URLs.

4.4 Connecting with Sigma

Sigma connects to Snowflake using the Go driver. When setting up a Snowflake connection, enable the Use Custom Host toggle, and enter your Yuki Proxy hostname in the Custom Hostname field. for example: acme-yuki-proxy.us-east-1.snowflakecomputing.com:443).

4.5 Connecting with Power BI Desktop

Power BI Desktop connects to Snowflake using the ODBC driver. Update the Server parameter to your Yuki Proxy hostname. For example: snowflake-locator.yukicomputing.com

4.6 Connecting with Python

When connecting via Python, include the host parameter in your connection function. Example:

con = snowflake.connector.connect(
  user = "[email protected]",
  password = "*******",
  account = "ron123" ,
  host = "snowflake-locator.yukicomputing.com"
)

4.7 Connecting with JDBC

To connect with the JDBC driver, override the host element in the JDBC URL with your Yuki Proxy hostname for Snowflake, and include the account parameter. For example, to connect to the abcd123 For example, to connect to the ron123 Snowflake account in AWS US East 1:

jdbc:snowflake://snowflake-locator.yukicomputing.com/[email protected]&account=ron123

4.8 Connecting with ODBC

To connect with the ODBC driver, override the server parameter with the Yuki Proxy hostname. For example: 

snowflake-locator.yukicomputing.com

Finish Setup

You’ve completed all onboarding steps - Yuki is now fully connected to your Snowflake environment. From this point, queries routed through your enabled warehouses will automatically be optimized by Yuki for cost and performance.

Next Step

Onboarding is complete - Yuki is now connected to your Snowflake environment. For details on encryption, access control, and data protection, proceed to: → General Security and Access Control

PreviousAdd User-Allowed IPsNextGeneral Security and Access Control

Last updated