What Moving Average does
Calculate rolling averages for trends. SQL syntax can vary by database, but the pattern below is a useful starting point for reports and analysis.
Syntax or pattern
AVG(amount) OVER (ORDER BY order_date ROWS BETWEEN 6 PRECEDING AND CURRENT ROW)5 practical examples
Use Moving Average in a sales report
Apply the Moving Average pattern to a sales table.
-- Moving Average example for sales
SELECT customer_id, order_date, total_amount
FROM orders
WHERE total_amount > 100;This shows how the Moving Average pattern can support a simple sales analysis.
Use Moving Average for customers
Apply the Moving Average pattern to customer records.
-- Moving Average example for customers
SELECT customer_id, email, status
FROM customers
WHERE status = 'Active';This is useful when customer records need filtering, labeling or summarizing.
Use Moving Average for products
Apply the Moving Average pattern to product or inventory data.
-- Moving Average example for products
SELECT product_id, product_name, category
FROM products;Product tables are good practice data for this SQL pattern.
Use Moving Average for monthly reporting
Apply the Moving Average pattern to a monthly reporting query.
-- Moving Average example for monthly reporting
SELECT DATE_TRUNC('month', order_date) AS month, SUM(total_amount) AS sales
FROM orders
GROUP BY DATE_TRUNC('month', order_date);This turns row-level transactions into a report-friendly result.
Use Moving Average during data checks
Apply the Moving Average pattern to find data quality issues.
-- Moving Average example for data checks
SELECT customer_id, COUNT(*) AS records
FROM orders
GROUP BY customer_id
HAVING COUNT(*) > 1;This is a useful pattern for auditing data before building a report.
Common mistakes to avoid
- Forgetting that SQL dialects vary across PostgreSQL, SQL Server, MySQL, BigQuery and SQLite.
- Using SELECT * in production reports when only a few columns are needed.
- Not checking join keys, duplicate rows or NULL values before trusting results.
FAQ
Will this SQL work in every database?
The idea is portable, but function names and date syntax may vary. Check your database dialect if a function is not recognized.
Should I use this in a report query?
Yes, if the pattern matches the business question and you have checked filters, joins and row counts.
Why does my result have too many rows?
The most common reasons are duplicate join keys, missing filters or grouping at the wrong level of detail.