N057-E2 Tier 4 · Advanced · easy analytics · Streamhub

Return each calendar day and the total number of `events` recorded on that day

Part of Grouping by Date Periods in SQL

The problem

Scenario: Streamhub's analytics team is reviewing platform activity at a daily level to identify high-traffic days.

Task: Write a query to return each calendar day and the total number of events recorded on that day.

Assumptions:

  • The events table holds one row per recorded event, with the timestamp stored in occurred_at.
  • A calendar day is identified by its date and covers every event recorded within that day.

Output:

  • One row per calendar day present in the data.
  • Columns in this order: day, event_count.
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

Run previews · Check grades

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

Worked solution Try it yourself first
Solution query
SELECT
  DATE_TRUNC('day', occurred_at)::date AS DAY,
  COUNT(*) AS event_count
FROM
  events
GROUP BY
  DATE_TRUNC('day', occurred_at)

The shape

date_trunc('day', occurred_at) reduces each event timestamp to midnight of its calendar day, which makes every event from the same day share one grouping key. COUNT(*) then runs once per day and returns one row per calendar day with the event volume for that day.

Clause by clause

  • SELECT date_trunc('day', occurred_at)::date AS day, COUNT(*) AS event_count returns one row per day. The ::date cast removes the midnight time component so the output column types as a date instead of a timestamp. COUNT(*) counts the events that fall inside the day.
  • FROM events reads every recorded event. There is no WHERE; every day with at least one event is in scope.
  • GROUP BY date_trunc('day', occurred_at) uses the same truncation as the grouping key. Two events recorded at 14:32 and 22:05 on the same date both truncate to that date at midnight and end up in the same group.

The trap

The GROUP BY has to repeat the date_trunc expression rather than reference the day alias. The alias defined in SELECT is not yet in scope when GROUP BY is evaluated, so GROUP BY day raises an error. Repeat the expression, or write GROUP BY 1 to reference the first SELECT column by position.

You practiced truncating a timestamp to its calendar day so all events sharing a day collapse into a single row.

How you actually get good at SQL

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

That's the whole SQLMaxx loop: 600+ real problems, instant AI feedback, mastery you can actually see, and spaced review that won't let you forget.

A stack of SQL practice problem cards, the top card showing an employees table.
615 problems · 66 concepts

Real problems. Not toy examples.

615 hand-built problems spanning all 66 concepts, from basic SELECTs to window functions, built on real schemas and real business questions, the kind you'll actually get asked on the job. Enough reps to make SQL automatic.

A retro computer showing a SQL query marked correct with a green checkmark.
Instant AI feedback

Write a query. Know if it's right in one second.

No copying an answer and hoping it clicked. The AI grader checks your real query against real data, catches exactly what's wrong, and explains the fix in plain English, like a senior analyst reading over your shoulder on every problem.

A circular mastery progress dial filling from blue to green, the SQLMaxx diamond at its center.
Mastery tracking

Stop guessing whether you actually know it.

SQLMaxx tracks every concept and shows you what you've mastered and what's still shaky. Your skills fill in one concept at a time, so 'I think I get joins' becomes something you can prove.

A SQL query editor circled by a blue return arrow with a clock, scheduled to come back for review.
Spaced review

Learn it once. Keep it for good.

Most of what you learn this week fades by next week. So when a concept comes due for review, SQLMaxx hands you a fresh problem to solve from a blank editor, not a flashcard to re-read. A research-backed spaced-repetition algorithm (FSRS) times each return for right before you'd forget, so your SQL is still there months later, when the interview or the job actually needs it.

Practice, feedback, mastery, review. That's the loop that turns reading into real skill.

Start free

No account, no credit card. Start solving in under a minute.