In SQL, z-score over the sample table is calculated with the query below. On the sample data it returns 4.04.
z = (Value − Mean) ÷ Standard deviation
Step by step
- Load daily.csv into a table called daily (day, ad_spend, website_orders, app_orders, avg_basket).
- Run the query and compare with the expected result.
CREATE TABLE daily (
day INTEGER,
ad_spend INTEGER,
website_orders INTEGER,
app_orders INTEGER,
avg_basket INTEGER
);The query
SELECT ROUND((d.website_orders - s.m) / s.sd, 2) AS z_day_17
FROM daily d,
(SELECT AVG(website_orders) AS m, STDDEV_SAMP(website_orders) AS sd FROM daily) s
WHERE d.day = 17;Expected result on the sample data: 4.04.
What the result means
Day 17 had 61 website orders. Its z-score is computed with a mean and standard deviation that include day 17 itself, which shrinks the score; leaving the day out of the baseline gives a much larger one.
Notes for SQL
- Tested on DuckDB. The same functions exist in PostgreSQL. SQLite and MySQL lack most statistical aggregates; compute in Python or load the data into DuckDB, which can query a CSV file directly.
- Statistical aggregates ignore NULL rows. Decide whether a missing day should be NULL (left out) or 0 (counted as a zero day).
Where z-score misleads
- Outliers inflate the standard deviation and so hide themselves. For outlier hunting, a robust rule (IQR, or median absolute deviation) is safer.
- The "beyond 3 is rare" rule assumes roughly normal data. Skewed data produces large z-scores routinely.
- Use the same standard deviation version (sample or population) consistently; STANDARDIZE takes whichever you give it.
The plain-language explanation is on the Z-score page.
The data
| day | website_orders |
|---|---|
| 1 | 24 |
| 2 | 27 |
| 3 | 22 |
| 4 | 30 |
| 5 | 28 |
| 6 | 25 |
| 7 | 31 |
| 8 | 29 |
| 9 | 26 |
| 10 | 33 |
| 11 | 30 |
| 12 | 28 |
| 13 | 35 |
| 14 | 32 |
| 15 | 29 |
| 16 | 34 |
| 17 | 61 |
| 18 | 31 |
| 19 | 36 |
| 20 | 33 |
| 21 | 30 |
| 22 | 37 |
| 23 | 35 |
| 24 | 32 |
| 25 | 38 |
| 26 | 36 |
| 27 | 34 |
| 28 | 40 |
| 29 | 37 |
| 30 | 39 |
Same method, other tools
Related methods
Learn more about SQL
- Python and SQL for data analysis, side by side — 3 min read
- Data analysis methods and techniques, and when to use each — 3 min read
About the data on this page
The figures come from a small made-up dataset, printed above in full so you can check every number by hand. Download it as daily.csv. The results are computed from those rows when the page is built, and the Excel formulas, SQL and Python on these pages are run against the same rows before publishing, so the code and the answers agree.
To get these numbers from your own data without writing formulas, try AnalyzeIt: ask in plain words and it shows the working behind every figure.
Legal entity
Devansh Yadav
Moradabad, Uttar Pradesh
Governing law: Courts at Moradabad, Uttar Pradesh
Phone: +91 8433475698
Legal: legal@analyzeit.in