The order in which you ROUND matters in SQL

Senior Data Engineer • Contractor / Freelancer • GCP & AWS Certified
Search for a command to run...

Senior Data Engineer • Contractor / Freelancer • GCP & AWS Certified
No comments yet. Be the first to comment.
Short, practical posts on SQL and BigQuery — from core language features to advanced query patterns. A reference for data practitioners at every level.
Here's a useful Dataform concept: pre_operations and post_operations. As the name implies, these represent a set of actions that run before and after the main operation (table, view, or SQL operations

BigQuery has always been a SQL engine for tabular data. Object tables add an interesting twist to that. Instead of rows containing values, an object table gives you one row per file — pointing at da

Query your data lake with warehouse-grade security and performance — without moving a single file.

Ever run a heavy BigQuery SQL query, processed gigabytes of data — and then accidentally closed the tab or forgot to save the results? 😬 Don't re-run it. Your results are still there. BigQuery automa

You can use query parameters in BigQuery hashtag#SQL (now in the console as well!) — but how are they different from variables, and when should you use each? Both parameters and variables act as place

Rounding numbers in SQL is one of the simplest operation, but it's important to we pay attention to how we apply it.
When you ROUND a value and then aggregate it using functions like SUM or AVG, the outcome may differ significantly compared to first aggregating the values and then rounding the result.
As with all things, take into consideration your context and business problem you're trying to solve.
ROUND - nearest integer or decimal place (if specified) 1.4 =1 but 1.5 =>2FLOOR - largest integer that is not greater than our value 1.7 => 1CEIL/CEILING - smallest integer than is not smaller than our value 1.4 => 2Found it useful? Subscribe to my Analytics newsletter at notjustsql.com.