Video | Tableau | Data prep | Tool strategy | Data engineering

Virtual connections: New in Tableau 2021.4

Virtual connections are basically the dream connection you could possibly create with Tableau.

Part ofWhat's new in Tableau 2021.4
Watch on YouTube
  • Virtual connections are a brand-new Tableau asset (not a published data source) that require the Data Management add-on and let you centralise connections, policies and row level security on server.
  • When saving, the Save button only stores a draft while Publish actually commits the connection and makes it available to users.
  • You can include multiple tables, use custom SQL, set live or extract per connection, and toggle table visibility to hide or show tables temporarily.
  • To connect from Desktop you must point to Tableau Server and pick the virtual connection from the dropdown; the server then delegates the live connection through to Snowflake.
  • The connection appears with a standard database icon rather than a server icon, which makes debugging confusing since edits must be made on the server.

Virtual connections are a new server-based asset in Tableau that let you centralise data connections, policies and row level security so users connect through a governed layer rather than building their own raw connections. I walk through creating one against Snowflake and using it from both Desktop and web edit.

This requires the Data Management add-on and a database you can connect to from Tableau Server (I use a Snowflake demo database set up in a prior video). A virtual connection is not a published data source — it's its own distinct asset type.

The Breakdown
  1. What a virtual connection actually is 0:00

    It's a brand-new asset type on server, separate from published data sources, that lets you build a connection once, apply policies and row level security to it, then place it in a project or collection for others to connect to from Desktop or web edit.

  2. Create the connection and pick tables 0:57

    From the New menu you choose Virtual Connections, pick a connector (only a limited set is available so far), log in, and select the tables you want to expose; you can also use custom SQL just as you would in Desktop.

  3. Review table metadata and set live vs extract 2:11

    Each table shows metadata — visibility, database, schema, live/extract status — which you can set globally or per table, plus a Tableau-prep-style preview so you can check the data is loading correctly before publishing.

  4. Save only drafts; Publish commits the change 5:28

    Save stores a draft that nobody else can use yet; you must hit Publish for the connection to actually become available to users. Get this order wrong and you'll assume changes are live when they aren't.

  5. Connect from Desktop via Tableau Server 6:34

    You must connect to Tableau Server (not a direct database connection) and select Virtual Connections from the dropdown; the server then delegates your access through to the underlying database live, and you can model relationships between the exposed tables as normal.

  6. Watch for the misleading connection icon 8:00

    A virtual connection shows a standard database icon in Desktop rather than a server icon, even though edits have to be made on the server — trying to edit the connection locally will just error out, so know where to actually go to fix it.

  7. Toggle table visibility to edit safely over time 9:12

    You can hide a table, make changes, save the draft, test it, then publish when ready — this lets you evolve a virtual connection (add data policies, tweak tables) over time without breaking things for existing users mid-edit.

  8. Same setup works in web edit 10:05

    Creating a new workbook in web edit and selecting the virtual connection gives you an identical experience to Desktop — pick the connection, drag in tables, and work as normal.

Worth Knowing
  • Save and Publish are not interchangeable: Save only stores a draft, Publish is what actually makes changes live.
  • The connection appears with a generic database icon in Desktop rather than a server icon, which is confusing since you can't actually edit it from there — you have to go back to the server.
  • Only a limited set of connectors is available at this stage, so if yours isn't listed you may need to wait for it or check the Tableau Exchange.
  • Row level security and data policies on virtual connections are covered in a separate video, not this one.
Use It When

Reach for this when you want one governed, centrally managed connection (with consistent tables, policies and future row level security) that many users and workbooks can connect to, instead of everyone building their own separate connections to the same source.

How this Rollup was made provenance & method

A Rollup is drafted by AI from the video's transcript, then reviewed and edited by Tim. Everything used to produce this one is listed below — the model, the exact prompt, and the source video — so the process is transparent and reproducible.

Transcription
On-device — NVIDIA Parakeet v3 for recent videos, OpenAI Whisper large-v3 for earlier ones. The transcript never leaves the machine or gets published.
Drafting
Claude Sonnet 5 in the cloud, from that transcript.
Prompt
The exact Rollup prompt (v2) — the full system prompt, unedited.
Source video
Watch on YouTube
Drafted
5 July 2026 at 09:38
Reviewed & edited
5 July 2026 at 09:41 · by Tim Ngwena

Model + prompt + video is everything you'd need to recreate a Rollup like this yourself. The one thing we don't share is the transcript.

Rights. The video and its transcript are the property of TN Media Ltd. Unauthorised use or download is prohibited. © TN Media Ltd.