Enterprise Plan Users — WHERE Clause in SQL

The problem

Streamhub's account management team is preparing for quarterly enterprise renewal discussions and needs a current subscriber list.

Write a query to return the name and email of every user on the enterprise plan.

Assumptions:

The users table contains every registered Streamhub user.
The plan column records each user's subscription tier; enterprise customers have plan set to 'enterprise'.

Output:

One row per enterprise user, with columns name and email.

Schema · analytics 5 tables

users

id integer

name text

email text

country text

plan text

signed_up_at timestamptz

is_active boolean

conversions

id integer

user_id integer

converted_at timestamptz

plan text

amount numeric

sessions

id integer

user_id integer

started_at timestamptz

ended_at? timestamptz

event_count integer

events

id integer

user_id integer

session_id? integer

event_type text

occurred_at timestamptz

properties? jsonb

periods

id integer

name text

start_month integer

end_month integer

Check answerShift Ctrl ↵

Run previews · Check grades

Write a query, then run it to see results here.

Worked solution Try it yourself first

Solution query

SELECT
  name,
  email
FROM
  users
WHERE
  plan = 'enterprise'

The shape

A string-equality filter on plan scopes the user table down to the one tier that matters for the renewal call. Every other plan — free, starter, pro — drops out before the result is shaped.

Clause by clause

SELECT name, email returns the two columns the account management team needs to schedule renewal outreach. Both come straight from the users table; no calculation, no transformation.
FROM users is the source — every registered Streamhub user, across every plan.
WHERE plan = 'enterprise' keeps only rows whose plan value is exactly the string 'enterprise'. The single quotes are required because the value is text; the comparison is case-sensitive, so 'Enterprise' or 'ENTERPRISE' would not match this filter against this column.

Why filter and not return all plans

The users table contains every plan tier mixed together. Without WHERE, the result would be the entire user base, which is the wrong scope for a renewal conversation about the enterprise tier specifically. A query that returns more rows than the business question asked about isn't "safer" — it's wrong in a different direction. The output goes into a renewal-prep deck; free-plan users in that list create work for the team to filter them out by hand.

The same shape recurs for any plan-tier analysis: swap the literal for 'pro', 'starter', or 'free' and the rest of the query stays the same. The structure is constant; the parameter changes.

You practiced filtering on a tier or category column to scope a query to one segment. Plan-tier filters are the everyday shape for any analysis split by subscription level.

Return the name and email of every user on the enterprise plan

The shape

Clause by clause

Why filter and not return all plans

Reading explains SQL. Writing it, over and over with instant feedback, is what makes you fluent.