Reseña del libro "SQL Analytics for Real-World Data (en Inglés)"
Knowing SQL syntax is not the same as knowing how to answer a business question correctly.A query can run perfectly and still produce the wrong number.A join can silently duplicate revenue. A retention calculation can change because of one misplaced filter. A rolling average can cover seven rows without covering seven days. A dashboard can report a perfectly calculated metric whose denominator nobody actually agreed on.The database did not make the mistake.The meaning was lost somewhere in the query.SQL Analytics for Real-World Data bridges the gap between knowing SQL commands and using SQL to produce reliable, decision-ready analysis.Instead of teaching isolated tricks on toy tables, this practical guide shows you how professional analysts reason through messy data, ambiguous business questions, changing grains, multiple relationships, incomplete records, and production-scale analytical workflows.Inside, you'll learn how to: Translate vague business questions into explicit analytical definitionsDefine the correct grain before joins, aggregations, and window calculationsPrevent fanout and metric duplication when combining one-to-many and many-to-many relationshipsChoose INNER, LEFT, EXISTS, anti-join, temporal, and reconciliation patterns based on analytical intentBuild trustworthy business metrics with clear populations, numerators, denominators, and time boundariesAvoid misleading averages, incorrect distinct counts, and aggregation errorsStructure complex analysis with readable, testable CTE pipelinesMaster window functions using partitioning, ordering, and explicit framesUse ranking, LAG, LEAD, running totals, rolling calculations, and share-of-total analysisBuild period-over-period and year-over-year reporting correctlyHandle missing dates, incomplete periods, business calendars, and timezone boundariesCreate cohort and retention analyses without confusing entry, activity, maturity, and reactivationBuild funnels that respect sequence, timing, repeated attempts, and session boundariesAnalyze customer behavior, repeat purchases, revenue concentration, subscriptions, MRR movement, and churnCalculate product engagement, service levels, throughput, backlog, operational latency, and percentile-based metricsDiagnose wrong query results systematically instead of adding DISTINCT and hoping for the bestImprove query performance using pruning, execution plans, cardinality awareness, indexing, pre-aggregation, and cost-aware designTurn ad hoc SQL into production analytics with tests, contracts, reconciliation, version control, freshness checks, and observabilityWrite analytical logic that remains understandable across PostgreSQL, SQL Server, MySQL, BigQuery, Snowflake, DuckDB, and other platformsWork effectively with semi-structured data, modern cloud warehouses, semantic layers, and AI-assisted SQLCommunicate results so that stakeholders understand not only the number, but exactly what the number meansThe book's central discipline is simple: Every query has a grain. Every metric has a definition. Every transformation changes meaning.The analyst's job is to control those changes deliberately.The manuscript reinforces this with a practical workflow: define, inspect, transform, validate, and present-rather than building a complicated final query first and trying to debug the answer afterward.The diagram on page 17 makes the same philosophy visual: business question → analytical definition → data transformation → validation → decision-ready result. SQL is only one part of the reasoning process.Don't just write SQL that runs. Write SQL that proves what the data means.
