Establishes a JDBC link from DBeaver to a Snowflake warehouse so you can browse objects and run SQL.
You need your Snowflake account name (e.g., acme.us-east-1
), user, password, role, default warehouse, database, and schema. Generate a network policy or use SSO if your org enforces it.
Open DBeaver ➜ Database ➜ Driver Manager ➜ Add ➜ Select “Snowflake” ➜ Download. The driver bundle ships with the latest JDBC library.
Format: jdbc:snowflake://<account>.snowflakecomputing.com/?warehouse=<wh>&db=<db>&schema=<schema>&role=<role>
. Supply user & password (or key-pair/SSO) in the Authentication tab.
Click “Test Connection.” A green check confirms driver load and network reachability. Hit “Finish” to store the profile.
Open a SQL Editor and run SELECT * FROM Customers LIMIT 10;
. Results should appear in the grid, proving the session’s default database objects are reachable.
Pin a small warehouse for ad-hoc work to avoid queueing. Enable “Keep-alive” in the driver’s properties so idle IDE tabs don’t drop. Use CLIENT_SESSION_KEEP_ALIVE=true
for long analyses.
Wrong account URL. Remove the extra region string—acme.us-east-1
, not acme.us-east-1.snowflakecomputing.com
. Mismatch throws HTTP 403
.
Warehouse spelling errors. The JDBC driver won’t auto-create warehouses; verify casing exactly matches the Snowflake object.
Use DBeaver’s SQL Console: USE ROLE ANALYST; USE DATABASE SALES_DB;
. The change is instant and scoped to the current session.
Yes. In the SQL Editor, right-click results ➜ Export Data ➜ CSV/Parquet. Schedule with DBeaver Tasks for recurring pulls.
Yes. Set authenticator=externalbrowser
in the JDBC URL. DBeaver will open a browser window for Okta or your IdP. After login, the IDE reuses the issued token.
Absolutely. Load your private key in the Authentication tab, choose “Key Pair,” and leave the password blank if the key is not encrypted.
Uncheck “Use SQL Limits” in the driver properties or raise the fetch size. Alternatively, paginate queries with LIMIT
to reduce memory pressure.