openskills.info
Snowflake Fundamentals logoCourse Preview

Snowflake Fundamentals

Snowflake is a cloud data platform for storing, querying, sharing, and governing data. It separates stored data from the compute clusters that process work, so teams can run different workloads without sharing the same compute resources.

itData engineering and analytics

Don't Panic — Snowflake Fundamentals

Snowflake is a managed cloud data platform for storing data, running analytical work, controlling access, and sharing selected data with other accounts. It saves you from tending a database server, which is pleasant, but it does not save you from deciding who can do what or why a query is spending money. The machine has been hidden. The choices have not.

The important trick is separation of storage and compute. Your tables stay in Snowflake-managed storage while a virtual warehouse, a cluster that runs queries and loads, wakes up only to do work. This means an ingestion job and an interactive reporting job can use different compute. It also means suspending a warehouse does not make its data evaporate in a tasteful puff of cloud.

The other idea is context. A database contains schemas, and schemas hold objects such as tables and views. A role receives object privileges, then reaches users through role grants. The active role in a session decides which SQL actions are allowed. A query that fails is therefore often not being dramatic; it may be using the wrong role, database, schema, or warehouse.

Sharing changes the usual copy-everything instinct. A provider creates a share and a consumer creates a read-only database from it. The data is not copied into the consumer account, but the consumer still uses its own compute to query it. Governance and data contracts remain very much on the guest list.

Costs follow the same map: compute, storage, and data transfer are separate usage types. Warehouse size and running time matter, so auto-suspend, budgets, and resource monitors are operating controls rather than decorative switches. Bigger compute may finish earlier while consuming credits at a higher rate. The sensible response is measurement, not an argument with the settings page.

Read the Intro when you need the full architecture and the limits of the platform. Use Slides for the layer and sharing diagrams, Cheatsheet for the object, role, and cost vocabulary, and Reference for the official path into loading, access control, and cost controls. Then use the practice session with a small dataset: the system becomes less mysterious once a table survives a suspended warehouse.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources