Getting Started: Account Setup, Web UI, and First Queries

Imagine you're a data analyst at a fast-growing e-commerce company. Your team is drowning in CSV files, and every query takes forever. You need a data warehouse that's fast, scalable, and easy to use—without managing servers. That's where Snowflake comes in. Snowflake is a cloud-native data platform that separates storage and compute, allowing you to scale independently and pay only for what you use. In this tutorial, you'll go from zero to running your first queries in minutes. We'll cover account setup, navigating the Snowsight web interface, creating virtual warehouses, loading sample data, and writing basic SQL. By the end, you'll have a solid foundation to start building your own data pipelines. Let's dive in!

1. Creating a Snowflake Account

To get started, navigate to signup.snowflake.com and sign up for a free 30-day trial. You'll need to provide your email, choose a cloud provider (AWS, Azure, or GCP) and region. After verification, you'll receive a URL like https://app.snowflake.com. This is your Snowsight interface. Once logged in, you'll see the classic Snowflake Web UI. For this tutorial, we'll use Snowsight (the new UI). If you see the classic UI, click 'Preview' to switch. Your account comes with a default warehouse (COMPUTE_WH), a database (SNOWFLAKE_SAMPLE_DATA), and a role (ACCOUNTADMIN). We'll use these to run our first queries.

-- Check your current role and warehouse
SELECT CURRENT_ROLE(), CURRENT_WAREHOUSE();

-- Set the warehouse if not set
USE WAREHOUSE COMPUTE_WH;

-- Explore sample data
SHOW DATABASES;
USE DATABASE SNOWFLAKE_SAMPLE_DATA;
SHOW SCHEMAS;

2. Navigating Snowsight (Web UI)

Snowsight is the modern web interface for Snowflake. The left sidebar contains: Home, Data (databases, schemas, tables), Worksheets (SQL editor), Warehouses (compute resources), Admin (users, roles, billing). The top bar shows your current role and warehouse. To create a new worksheet, click 'Worksheets' > '+' > 'New Worksheet'. This opens a SQL editor with syntax highlighting and query history. You can also browse sample data by clicking 'Data' and expanding databases. Let's explore the TPCH_SF1 schema.

-- List tables in TPCH_SF1
USE SCHEMA TPCH_SF1;
SHOW TABLES;

-- Describe a table
DESC TABLE CUSTOMER;

-- Preview data
SELECT * FROM CUSTOMER LIMIT 10;

3. Understanding Virtual Warehouses

A virtual warehouse is a cluster of compute resources (CPU, memory, storage) that executes queries. You can create multiple warehouses of different sizes (X-Small to 6X-Large) and set them to auto-suspend after inactivity. This decouples compute from storage, so you only pay for compute when queries run. To create a warehouse, go to Admin > Warehouses > + Warehouse. Give it a name, choose size, and set auto-suspend (e.g., 5 minutes). You can also create warehouses via SQL.

-- Create a warehouse
CREATE WAREHOUSE my_wh
  WITH WAREHOUSE_SIZE = 'XSMALL'
  AUTO_SUSPEND = 300
  AUTO_RESUME = TRUE
  INITIALLY_SUSPENDED = TRUE;

-- Use the warehouse
USE WAREHOUSE my_wh;

-- Alter warehouse (e.g., resize)
ALTER WAREHOUSE my_wh SET WAREHOUSE_SIZE = 'SMALL';

-- Drop warehouse (if not needed)
DROP WAREHOUSE IF EXISTS my_wh;

4. Creating Databases and Schemas

Databases are logical containers for schemas, which contain tables, views, and other objects. You can create databases and schemas with simple SQL. Snowflake also supports cloning databases for zero-copy cloning, which is useful for creating development environments. Let's create a database for our e-commerce example.

-- Create a database
CREATE DATABASE IF NOT EXISTS ecommerce_db;

-- Create a schema
CREATE SCHEMA IF NOT EXISTS ecommerce_db.raw_data;

-- Use the schema
USE SCHEMA ecommerce_db.raw_data;

-- Create a table
CREATE TABLE customers (
  customer_id INTEGER PRIMARY KEY,
  name VARCHAR(100),
  email VARCHAR(100),
  signup_date DATE
);

-- Insert sample data
INSERT INTO customers VALUES
  (1, 'Alice', 'alice@example.com', '2023-01-15'),
  (2, 'Bob', 'bob@example.com', '2023-02-20');

-- Query the table
SELECT * FROM customers;

5. Loading Data into Snowflake

Snowflake supports loading data from files (CSV, JSON, Parquet) via stages. A stage is a location where data files are stored, either internal (Snowflake-managed) or external (S3, Azure Blob). You can use the PUT command to upload files to a stage, then COPY INTO to load into a table. For this tutorial, we'll use a simple CSV file. First, create a file format and stage.

-- Create a file format for CSV
CREATE FILE FORMAT csv_format
  TYPE = 'CSV'
  FIELD_OPTIONALLY_ENCLOSED_BY = '"'
  SKIP_HEADER = 1;

-- Create an internal stage
CREATE STAGE my_stage
  FILE_FORMAT = csv_format;

-- Upload file (using Snowsight or CLI)
-- In Snowsight: Data > Databases > ecommerce_db > Stages > my_stage > + Upload
-- Or using SnowSQL: PUT file:///path/to/orders.csv @my_stage;

-- Create table for orders
CREATE TABLE orders (
  order_id INTEGER,
  customer_id INTEGER,
  order_date DATE,
  amount DECIMAL(10,2)
);

-- Load data from stage
COPY INTO orders
  FROM @my_stage/orders.csv
  FILE_FORMAT = csv_format
  ON_ERROR = 'CONTINUE';

-- Verify
SELECT * FROM orders;

6. Running Your First Queries

Now that we have data, let's run some analytical queries. Snowflake supports standard SQL with extensions for analytics. We'll explore joins, aggregations, and window functions. Let's find total sales per customer.

-- Join customers and orders
SELECT c.name, SUM(o.amount) AS total_spent
FROM customers c
JOIN orders o ON c.customer_id = o.customer_id
GROUP BY c.name
ORDER BY total_spent DESC;

-- Use a window function to rank customers
SELECT name, total_spent,
  RANK() OVER (ORDER BY total_spent DESC) AS rank
FROM (
  SELECT c.name, SUM(o.amount) AS total_spent
  FROM customers c
  JOIN orders o ON c.customer_id = o.customer_id
  GROUP BY c.name
);

7. Managing Roles and Permissions

Snowflake uses role-based access control (RBAC). The default roles are: ACCOUNTADMIN (full access), SECURITYADMIN (manage roles), SYSADMIN (create warehouses/databases), USERADMIN (manage users), PUBLIC (default for all users). Best practice: create custom roles with least privilege. For example, create a role 'analyst' that can only SELECT from specific schemas.

-- Create a custom role
CREATE ROLE analyst;

-- Grant usage on database and schema
GRANT USAGE ON DATABASE ecommerce_db TO ROLE analyst;
GRANT USAGE ON SCHEMA ecommerce_db.raw_data TO ROLE analyst;

-- Grant SELECT on all tables in schema
GRANT SELECT ON ALL TABLES IN SCHEMA ecommerce_db.raw_data TO ROLE analyst;

-- Create a user and assign role
CREATE USER analyst_user
  PASSWORD = 'strong_password'
  DEFAULT_ROLE = analyst
  MUST_CHANGE_PASSWORD = TRUE;

GRANT ROLE analyst TO USER analyst_user;

8. Monitoring Usage and Costs

Snowflake provides account usage views and information schema to monitor queries, warehouse usage, and storage. The ACCOUNT_USAGE schema contains views like QUERY_HISTORY, WAREHOUSE_METERING_HISTORY, and STORAGE_USAGE. You can also set resource monitors to cap credit consumption.

-- View recent queries
SELECT query_text, warehouse_size, credits_used_cloud_services
FROM SNOWFLAKE.ACCOUNT_USAGE.QUERY_HISTORY
WHERE start_time > DATEADD('day', -1, CURRENT_TIMESTAMP())
ORDER BY start_time DESC
LIMIT 10;

-- Check warehouse credit usage
SELECT warehouse_name, SUM(credits_used) AS total_credits
FROM SNOWFLAKE.ACCOUNT_USAGE.WAREHOUSE_METERING_HISTORY
WHERE start_time > DATEADD('day', -7, CURRENT_TIMESTAMP())
GROUP BY warehouse_name;

-- Create a resource monitor
CREATE RESOURCE MONITOR daily_limit
  WITH CREDIT_QUOTA = 100
  FREQUENCY = 'DAILY'
  START_TIMESTAMP = '2024-01-01 00:00:00'
  TRIGGERS ON 80 PERCENT DO NOTIFY
            ON 100 PERCENT DO SUSPEND;

ALTER WAREHOUSE my_wh SET RESOURCE_MONITOR = daily_limit;