Video | Snowflake | Data engineering | Analytics

Setup Visual Studio Code for Snowflake | Learn Snowflake

If you're already in VS Code doing data work, here's how to query Snowflake without ever leaving the editor.

Part ofGetting Started with Snowflake
Watch on YouTube
  • You need to install the SQL Tools extension first, as it's the engine the Snowflake driver relies on to use VS Code as a database client
  • The Snowflake account identifier is your account ID plus region, obtained by stripping everything from .snowflakecomputing.com onwards and from the start of your login URL
  • A connection requires a name, account identifier, username, password, database and warehouse, and you can verify it with the Test Connection button before saving
  • SQL Tools stores connection settings as JSON, and you should check where this is kept since credentials may be stored as plain text
  • The SQL Tools view only loads the first 50 rows, and a session history pane lets you retrieve and re-run any previous queries

You can query Snowflake directly from Visual Studio Code by installing two extensions and configuring one connection, avoiding the need to switch tools for basic SQL work.

Tim starts from a vanilla VS Code install with no extensions configured, then connects it to an existing Snowflake account and database.

The Breakdown
  1. Install SQL Tools first 0:22

    Search the VS Code extensions marketplace for SQL Tools and install it. This must come first because it's the underlying engine that database-specific drivers, including Snowflake's, plug into to turn VS Code into a database client.

  2. Add the Snowflake driver 1:17

    With SQL Tools installed, search extensions for Snowflake and install the driver that's tagged as an SQL Tools driver. Once installed, Snowflake appears as an option when you add a new connection inside the SQL Tools panel.

  3. Start a new connection 2:04

    Open SQL Tools, add a new connection, choose Snowflake as the driver and give the connection a name of your choosing.

  4. Get the account identifier right 2:15

    Copy your Snowflake login URL, strip everything after .snowflakecomputing.com and everything before the account portion, and what remains is your account identifier (account name plus region). Tim flags this as a step people commonly get wrong, so it's worth double-checking each time.

  5. Fill in the remaining connection details 3:02

    Beyond the account identifier, you need username, password, database name and warehouse to complete the connection — Tim recommends keeping these noted somewhere so you're not retyping them each time.

  6. Test before you save 3:21

    Use the Test Connection button at the bottom of the setup form before saving; a successful test shows a green confirmation, which tells you the details are correct before you commit to using it.

  7. Check where credentials are stored 3:41

    SQL Tools saves each connection as JSON on your machine. It's worth checking independently whether this is stored as plain text, since that has security implications if you're storing real passwords.

  8. Run queries and reuse history 4:21

    Clicking a saved connection opens a blank SQL canvas where you can write and run standard SQL against your database and schema. The results view only loads the first 50 rows even if more were affected, and a session history pane on the left lets you find and re-run any earlier query without retyping it.

Worth Knowing
  • The SQL Tools results view caps at 50 rows even when a query affects more, so don't assume you're seeing the full result set
  • Connection credentials are stored locally as JSON — Tim wasn't sure at the time whether this is plain text, so it's worth confirming before storing real passwords
  • Getting the account identifier wrong (not stripping the URL correctly) is a common stumbling block worth double-checking
  • Query history for the session is preserved even if you close a SQL tab, so you don't lose work by closing a window
Use It When

Reach for this when you're already working in VS Code for other data tasks and want to run quick SQL checks against Snowflake without switching to a separate client.

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.