Install SnowSQL, configure connection parameters, and run test queries to start using Snowflake from a Windows machine.
Download the SnowSQL command-line client (Windows MSI) from the Snowflake web interface. SnowSQL lets you authenticate, run DDL/DML, and script workflows locally.
Run the MSI with admin rights. Accept the license, choose an install path, and keep the default for environment variables so snowsql.exe is added to PATH.
Create a named connection in %USERPROFILE%\.snowsql\config
or supply parameters inline.Store account
, user
, warehouse
, database
, and role
.
Open PowerShell or CMD and run snowsql -a <account> -u <user>
. Enter the password when prompted. A *>
prompt confirms success.
Execute the DDL in SnowSQL or the Snowflake Web UI.Use the syntax section below for ready-to-run statements that mirror a typical storefront schema.
Stage CSV files in an S3 bucket or local stage, then run COPY INTO
. Specify FILE_FORMAT = (TYPE = 'CSV' FIELD_OPTIONALLY_ENCLOSED_BY='"')
for clean ingestion.
Continue in SnowSQL or connect IDEs (DBeaver, Galaxy) via the Snowflake JDBC driver.Use SQL exactly as you would in the cloud UI.
Keep SnowSQL updated with snowsql -v
. Protect credentials using Windows Credential Manager. Automate recurring jobs with Task Scheduler.
Invalid certificate errors arise on outdated Windows versions—install the latest root certificates."Unknown host" means the account URL is misspelled.
Visit docs.snowflake.com or use Galaxy’s AI copilot to generate, optimize, and share your Snowflake queries.
.
No. SnowSQL requires write access to Program Files
and PATH. Ask IT for temporary elevation.
Yes. The Windows setup adds CLI access only. You can continue using Snowflake’s web UI or any IDE via JDBC/ODBC.
Download the latest MSI and reinstall, or run snowsql -u
if auto-update is enabled in your config.