Warehouse and analytical
Snowflake
Snowflake is documented as a SQL-first warehouse workflow with account/project posture, query history, credits, warehouses, stages, shares, and clone/copy previews.
Prerequisites
- Install the current DataPad++ desktop pre-release on Windows, macOS, or Linux.
- Have the endpoint, database file, or cloud account details for a Snowflake datastore you are authorized to use. Start with least-privileged, read-only access.
- Keep an independent backup before enabling edits, administration, restore, or transfer execution.
Connect and run a safe query
- 1
Create the connection
Open Library, choose Create connection, and select Snowflake and a supported Connection method tab.
- 2
Test and save
Complete the applicable fields and enable Read-only connection. Test connection when available; new local files and pending secondary credential changes must be saved first. Review runtime limitations and warnings.

Snowflake connection setup. The Snowflake connection dialog with supported method tabs and illustrative, non-secret settings. Expand optional sections and review runtime limitations before saving. Open full size - 3
Open the native explorer
Use Save Connection, or Create Database and Save Connection for a new local file, then open the Snowflake Explorer where supported.
- 4
Select a scope
Select the database / schema scope that should be attached to the new tab.
- 5
Run a bounded read
Open a query tab, paste the bounded read-only sample below, and choose Run or press Ctrl/Cmd+Enter.

Snowflake native workflow. A representative Snowflake explorer and bounded read-only workflow. Replace the example objects with names from your datastore. Open full size - 6
Inspect the result
Inspect Results, Messages, History, and Details; dock the panel on the bottom or right as needed.
- 7
Export when needed
Export only the required rows after reviewing format, destination, and redaction options.
- 8
Open diagnostics or transfers
Open Diagnostics or Transfers from the drawer/status bar and treat disabled reasons as capability boundaries, not transient errors.
Connection fields
| Field | Required | Purpose | Safe example |
|---|---|---|---|
| Name | Yes | A clear profile name, without credentials. | Snowflake development |
| Connection method | Yes | Choose a supported tab. The fields below apply only to the selected method and deployment. | Cloud / endpoint settings / Connection string |
| Environment | No | Attach the intended variable and safety context. | Local development |
| Read-only connection | No | Enable for initial exploration. This does not make pre-release software safe for production workloads. | Enabled |
| Host / Port | No | Endpoint for a fields-based connection. Follow the selected deployment and runtime limitations; MongoDB SRV does not use an explicit port. | localhost / engine default |
| Database / default scope | No | Initial scope for browsing, where supported. | catalog |
| Complete connection string | Yes | Required in Connection string mode only. Saved unchanged as one vault secret with Save Connection. Blank keeps an existing stored value. | Paste your complete provider string; do not share it |
| Username | No | Authentication identity for the selected method. | catalog_reader |
| Password | No | Required only when the chosen authentication needs it. Save Connection stores changes; blank preserves an existing value, and Reveal… explicitly discloses it. | Stored in the desktop OS vault |
| Contract endpoint | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Account | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Project | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Dataset | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Database | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
| Schema | No | General. Optional, depending on the method and server. Review runtime limitations before overriding the driver default. | Driver default |
Run the sample query
SELECT order_id, customer_id, total
FROM DEMO.PUBLIC.ORDERS
ORDER BY order_id
LIMIT 25;Explore and inspect
- Browse databases, schemas, tables, views, stages, warehouses, jobs/query history, shares, streams, tasks, roles, grants, storage, compute, and diagnostics.
- Inspect result grids, query-history rows, credit usage, warehouse load, storage posture, access details, raw SQL messages, and scan/cost warnings.
Diagnose, administer, and transfer
- Review query history, credit usage, warehouse load, utilization, storage/compute posture, access, shares, stages, reservations-like posture, and cost signals.
- Preview warehouse suspend/resume, clone/copy, stage workflows, grants, role changes, import/export, unload/load, and guarded drop plans.
- Import — Plan only. Snowflake loads and unloads through named stages with COPY INTO. Formats: CSV (portable-lossy), JSON (portable), Parquet (native). Destinations: named stage, cloud uri. Live Snowflake transfer requires an authenticated SQL transport, a configured named stage, and opt-in validation against a real Snowflake account.
- Export — Plan only. Snowflake loads and unloads through named stages with COPY INTO. Formats: CSV (portable-lossy), JSON (portable), Parquet (native). Destinations: named stage, cloud uri. Live Snowflake transfer requires an authenticated SQL transport, a configured named stage, and opt-in validation against a real Snowflake account.
- Backup — Plan only. Snowflake uses zero-copy clone and Time Travel recovery. Formats: Native managed backup (native). Destinations: managed restore, cloud uri. Snowflake clone and Time Travel recovery require an authenticated SQL transport, recovery-enabled source objects, and opt-in validation against a real Snowflake account.
- Restore — Plan only. Snowflake uses zero-copy clone and Time Travel recovery. Formats: Native managed backup (native). Destinations: managed restore, cloud uri. Snowflake clone and Time Travel recovery require an authenticated SQL transport, recovery-enabled source objects, and opt-in validation against a real Snowflake account.

Capabilities and availability
| Capability | Status | Notes |
|---|---|---|
| Native explorer | Preview | Browse databases, schemas, tables, views, stages, warehouses, jobs/query history, shares, streams, tasks, roles, grants, storage, compute, and diagnostics. |
| Read queries | Preview | Run scoped Snowflake SQL, table SELECT builders, deterministic SQL IntelliSense, bounded query starts, query history helpers, and cost-aware previews. |
| Inline editing | Guarded | Requires key evidence, a writable profile, and environment confirmation. |
| Diagnostics / administration | Guarded | Preview warehouse suspend/resume, clone/copy, stage workflows, grants, role changes, import/export, unload/load, and guarded drop plans. |
| Import / export / transfer | Guarded | Availability follows the authoritative runtime transfer manifest and shows a disabled reason when execution is not implemented. |
Safety and limitations
Troubleshooting
| Symptom | Resolution |
|---|---|
| Test connection fails or times out | Verify endpoint, port, TLS mode, proxy settings, service health, firewall rules, and network access. Keep the profile unsaved until the test explains the failure. |
| Explorer branches are empty or disabled | Confirm the selected database / schema, refresh the branch, and grant the minimum metadata permissions described in the connection warning. |
| Run, edit, admin, or transfer is disabled | Read the visible disabled reason. Select a compatible target, turn off read-only only when authorized, or use the documented preview/export fallback. |
| The sample query fails or returns different columns | Replace the example names with objects from your Snowflake datastore, confirm the selected database / schema, and keep the query bounded while you validate the result. |