Skip to content
Tutorials Center
My learning

Topics

Lesson 2 of 38 ยท Getting Started

Accounts, Editions and the Web UI

Understand Snowflake accounts, regions, editions and credits, set up a free trial, and find your way around Snowsight, the web interface, plus SnowSQL and drivers.

Before you write a query you need an account. An account is your private Snowflake environment: its own users, roles, databases, warehouses and bill. This lesson explains what an account is made of, how editions and regions affect you, how to get a free trial, and how to find your way around the web interface.

What is in an account

Think of an account as a building:

  • A cloud provider and region decide where the data physically lives (for example AWS in Frankfurt). Pick a region close to your users and compliant with your data-residency rules.
  • An organization can contain many accounts, which is how large companies separate production from development or one business unit from another.
  • Inside the account live users, roles, databases, warehouses and other objects.

Your account has a unique identifier. You see it in the sign-in URL and in connection tools, usually in the form organization-account. The older locator format looks like xy12345.eu-central-1. Both identify the same thing.

Editions

Snowflake sells several editions. Higher editions include everything below them.

Edition Highlights
Standard Core SQL warehouse, Time Travel of 1 day, secure data sharing
Enterprise Time Travel up to 90 days, multi-cluster warehouses, column and row security policies, materialized views
Business Critical Stronger encryption options, private connectivity, compliance features for regulated data
Virtual Private Snowflake A fully separate environment for the most sensitive workloads

Features and limits change over time, so check the current pricing page when you decide. Whichever edition you pick, the SQL you write is the same. Editions mostly decide which advanced features are switched on.

Many examples later in the course (multi-cluster warehouses, row access policies, 90-day Time Travel) need Enterprise edition or above. The lessons say so each time.

Credits and how billing works

Snowflake bills you in credits for compute and in terabytes per month for storage. A running warehouse burns credits per second (with a one-minute minimum each time it resumes). A bigger warehouse burns more credits per hour but finishes work faster. Warehouses and Cost covers the sizes, and the cost chapter at the end of the course returns to monitoring.

For now remember: an idle, suspended warehouse costs nothing for compute. Storage is billed regardless.

Get a free trial

You can create a trial account at the Snowflake website. You pick a cloud, a region and an edition, and you receive a credit allowance that lasts for a limited time. No example in this course needs more than a tiny fraction of it. When you sign up you are asked for an email, and you receive a link to activate and choose a password. Never share your password or paste it anywhere.

Snowsight: the web interface

You work in a browser interface called Snowsight. The left menu groups things as follows (names can shift between releases):

  • Projects โ†’ Worksheets: where you write SQL. Each worksheet has a role, warehouse, database and schema selector at the top.
  • Data โ†’ Databases: browse databases, schemas, tables and columns, and preview rows.
  • Data Sharing / Marketplace: share data or get datasets from others.
  • Monitoring โ†’ Query History: every query, its duration, bytes scanned and the warehouse that ran it.
  • Admin โ†’ Warehouses, Users & Roles, Cost Management: administration.
flowchart LR
  A["Browser<br/>Snowsight"] --> B["Cloud services<br/>layer"]
  C["SnowSQL / drivers<br/>Python, JDBC, ODBC"] --> B
  B --> D["Virtual<br/>warehouse"]
  D --> E["Data in<br/>storage"]

Every client, from the web UI to a Python script, talks to the same cloud services layer.

Other ways to connect

You are not limited to the browser:

  • Snowflake CLI and the older SnowSQL are command-line clients.
  • Drivers for Python, JDBC, ODBC, Node.js, Go, .NET and others let applications run queries.
  • BI tools such as Tableau, Power BI and Looker connect through the same drivers.
  • Snowpark lets you write Python, Java or Scala that runs inside Snowflake (covered later in the course).

Here is how a connection looks in the Python connector. It is read-only because it needs real credentials:

Python
# Snowflake Python connector (read-only)
import snowflake.connector

conn = snowflake.connector.connect(
    account="myorg-myaccount",
    user="LEARNER",
    password="...",        # use key-pair auth or SSO in real projects
    warehouse="LEARN_WH",
    database="BOOKSHOP",
    schema="SALES",
)
cur = conn.cursor()
cur.execute("SELECT CURRENT_VERSION()")
print(cur.fetchone())

In real projects prefer key-pair authentication, OAuth or single sign-on over passwords, and keep secrets out of source code.

Context: role, warehouse, database, schema

Every worksheet session has four pieces of context. A query needs all four to be sensible: a role that has the privilege, a warehouse to run on, and the database and schema where unqualified names are looked up.

SQL
-- Snowflake SQL (read-only)
USE ROLE SYSADMIN;
USE WAREHOUSE learn_wh;
USE DATABASE bookshop;
USE SCHEMA sales;

SELECT CURRENT_ROLE(), CURRENT_WAREHOUSE(), CURRENT_DATABASE(), CURRENT_SCHEMA();

If you see an error like "No active warehouse selected," you forgot USE WAREHOUSE. If you see "Object does not exist or not authorized," your role lacks a privilege or you are in the wrong schema. Those two errors account for a large share of beginner trouble.

The stand-in below mimics fully qualified names. In-browser SQLite has no databases and schemas, so the example uses table aliases to show the idea that a name can be written with or without its prefix:

SQL Stand-in: qualified versus unqualified names ยท database: bookstore

Press Run (or Ctrl + Enter) to see the result here.

A second stand-in: SQLite can show which "session context" a query used by storing it in a small table. This is just a model of the idea that context is state:

SQL Stand-in: session context as a table

Press Run (or Ctrl + Enter) to see the result here.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does a Snowflake account contain?

    An account is a self-contained environment in a cloud region, with its own objects, security and bill.
  2. 2. Which edition is needed for multi-cluster warehouses and Time Travel beyond one day?

    Enterprise adds up to 90 days of Time Travel and multi-cluster warehouses. Standard has 1 day of Time Travel.
  3. 3. You run a query and see 'No active warehouse selected'. What is the likely fix?

    Queries need compute. Select a warehouse for the session with USE WAREHOUSE or the worksheet selector.
  4. 4. When is a suspended warehouse billed for compute?

    Compute credits are consumed only while a warehouse is running. Storage is billed separately.

Summary

  • An account lives in one cloud region and holds users, roles, databases and warehouses.
  • Editions control which advanced features you have; the SQL stays the same.
  • Compute is billed in credits per second while a warehouse runs; storage is billed separately.
  • Snowsight is the web UI; the Snowflake CLI, SnowSQL, drivers and BI tools reach the same service.
  • Every session has a role, warehouse, database and schema context. Most beginner errors come from missing one.

Next: Your First Queries in Worksheets