Tableau

Point Tableau at your gateway address by changing the Server field in the Snowflake or Databricks connector. Everything else — your workbooks, your data sources, your scheduled refreshes — keeps working unchanged.

Change the Server field

Open the data source connection in Tableau and update the Server field on the Snowflake or Databricks connector. Role, Warehouse, Database, and Schema stay the same.

Server: your-account.snowflakecomputing.com
Role:   ANALYST
Warehouse: REPORTING_WH
Database:  ANALYTICS

Server: your-slug.gateway.airbrx.ai
Role:   ANALYST
Warehouse: REPORTING_WH
Database:  ANALYTICS

For Databricks the field is similarly your Server Hostname — replace it with the gateway address. HTTP Path stays as-is because the Gateway forwards that part of the request to your warehouse unchanged.

Authentication

Use the same Snowflake or Databricks credentials you've always used — username and password, key-pair, OAuth, or personal access token. The Gateway forwards them straight to your warehouse without storing or inspecting them.

• Username + password — the most common Tableau auth mode for Snowflake; works as-is.
• Key-pair — point Tableau at your private key file as before; the Gateway passes the auth challenge through.
• OAuth or token-based auth — Snowflake OAuth, Databricks PAT, OAuth, or (on Azure-hosted workspaces) AAD. The handshake completes against your warehouse, not Airbrx.

Verify the cache is doing work

Tableau doesn't surface HTTP response headers in its own UI, so use the App traffic page — every query Tableau sends shows up with its cache outcome and rule match. From the App, you can also see the underlying response headers for any individual statement:

See the response headers reference for the full list, or analytics API if you'd rather pull cache metrics into a Tableau dashboard about Tableau itself.

Notes worth knowing

• Live vs Extract. Live connections benefit from caching on every render — every dashboard refresh that asks the same questions hits cache. Extract refreshes pull a snapshot through the Gateway once; subsequent renders go to the local extract, not the Gateway.
• Metadata queries. Tableau issues a lot of describe table / list columns queries when authoring a data source. Those are excellent caching candidates and pay off on every author-and-edit round-trip.
• Per-user isolation. If your dashboards rely on warehouse RLS, configure your cache rules to key per user — otherwise cache hits could surface another user's filtered view. The rules analyzer in the App flags this for you.
• Driver compatibility. The Gateway is wire-compatible with Snowflake and Databricks, so Tableau's bundled drivers work with no swap.

Where to go next

• Rules as the differentiator — how to write cache rules that match your dashboard query patterns.
• Response headers reference — full list of X-Airbrx-* headers.
• Other connection recipes.