SQL's LAG and LEAD functions are used to access row data with specified offsets before and after the current row. 1. LAG(column, offset, default) Gets the value of the offset line before the current line. The default offset is 1. If it does not exist, it returns NULL or specify the default value; 2. LEAD(column, offset, default) Gets the value of the offset line after the current line. The usage is similar to LAG; 3. The basic syntax is to calculate adjacent records by sorting or grouping in combination with OVER clauses, such as viewing sales of the previous month and the next month by date; 4. Group calculations can be implemented through PARTITION BY, such as analyzing trends by region and product classification; 5. Trend changes can be judged in conjunction with CASE WHEN, such as sales growth, decline or flatness. It is also recommended to use CTE to avoid repeated calculations to optimize performance. Mastering these key points can be effectively used in scenarios such as time series analysis, month-on-month comparison and abnormal detection.
SQL's LAG and LEAD functions are window functions that access a row of data before or after the current row. They are particularly useful when analyzing time series, trend changes, or comparing adjacent records. Below are some common usage scenarios and examples to help you quickly understand the actual usage of these two functions.

1.What are LAG and LEAD?
-
LAG(column, offset, default)
: Get the value ofoffset
line up (first) of the current line, the default is 1. -
LEAD(column, offset, default)
: Get the value ofoffset
line down (after) of the current line, the default is 1.
To give a simple example:
Suppose you have a sales record table, sorted by month. If you want to know the comparison between "this month's sales" and "last month", you can use LAG()
; if you want to see "next month", you can use LEAD()
.

2. Basic syntax structure
SELECT date, Sales, LAG(sales, 1) OVER (ORDER BY date) AS prev_sales, LEAD(sales, 1) OVER (ORDER BY date) AS next_sales FROM sales_data;
In the example above:
- After sorting by
date
, each row can see sales for the previous month and the next month. - If there is no corresponding value (such as the first line does not have the previous one), the default return NULL.
You can specify default values as needed, for example:

LAG(sales, 1, 0) OVER (ORDER BY date)
This way, when the previous line does not exist, it will return 0 instead of NULL.
3. Use LAG/LEAD in grouping
In actual business, different categories are often processed separately, such as viewing trends by region and product classification.
SELECT region, date, Sales, LAG(sales, 1, 0) OVER (PARTITION BY region ORDER BY date) AS prev_sales FROM regional_sales;
The key point here is to add PARTITION BY region
, indicating that the value of the previous row is calculated separately within each region.
Common application scenarios include:
- Daily sales comparison of different stores
- Time difference between users
- Analysis of price changes of multiple products
4. Trend analysis based on condition judgment
With the data from before and after lines, you can further make logical judgments, such as judging whether sales have increased.
SELECT date, Sales, LAG(sales) OVER (ORDER BY date) AS prev_sales, CASE WHEN sales > LAG(sales) OVER (ORDER BY date) THEN 'Increase' WHEN sales < LAG(sales) OVER (ORDER BY date) THEN 'Decrease' ELSE 'Same' END AS trend FROM sales_data;
This way you can directly see the trend changes every day. Note that since LAG is a window function, it is a bit troublesome to write repeatedly in CASE, but this is standard practice.
Some optimization suggestions:
- If the query is complicated, consider first using CTE or subquery to calculate the LAG value before judging
- Avoid calling the same LAG/LEAD multiple times in the same query, affecting performance
Basically that's it. LAG and LEAD seem simple, but are very practical in actual analysis, especially when you need to do tasks such as month-on-month, trend judgment, and abnormal detection. By mastering the sorting method and partitioning logic, you will be able to flexibly deal with various scenarios.
The above is the detailed content of SQL LAG and LEAD function examples. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

OLTPisusedforreal-timetransactionprocessing,highconcurrency,anddataintegrity,whileOLAPisusedfordataanalysis,reporting,anddecision-making.1)UseOLTPforapplicationslikebankingsystems,e-commerceplatforms,andCRMsystemsthatrequirequickandaccuratetransactio

Toduplicateatable'sstructurewithoutcopyingitscontentsinSQL,use"CREATETABLEnew_tableLIKEoriginal_table;"forMySQLandPostgreSQL,or"CREATETABLEnew_tableASSELECT*FROMoriginal_tableWHERE1=2;"forOracle.1)Manuallyaddforeignkeyconstraintsp

To improve pattern matching techniques in SQL, the following best practices should be followed: 1. Avoid excessive use of wildcards, especially pre-wildcards, in LIKE or ILIKE, to improve query efficiency. 2. Use ILIKE to conduct case-insensitive searches to improve user experience, but pay attention to its performance impact. 3. Avoid using pattern matching when not needed, and give priority to using the = operator for exact matching. 4. Use regular expressions with caution, as they are powerful but may affect performance. 5. Consider indexes, schema specificity, testing and performance analysis, as well as alternative methods such as full-text search. These practices help to find a balance between flexibility and performance, optimizing SQL queries.

IF/ELSE logic is mainly implemented in SQL's SELECT statements. 1. The CASEWHEN structure can return different values ??according to the conditions, such as marking Low/Medium/High according to the salary interval; 2. MySQL provides the IF() function for simple choice of two to judge, such as whether the mark meets the bonus qualification; 3. CASE can combine Boolean expressions to process multiple condition combinations, such as judging the "high-salary and young" employee category; overall, CASE is more flexible and suitable for complex logic, while IF is suitable for simplified writing.

SQL'spatternmatchinghaslimitationsinperformance,dialectsupport,andcomplexity.1)Performancecandegradewithlargedatasetsduetofulltablescans.2)NotallSQLdialectssupportcomplexregularexpressionsconsistently.3)Complexconditionalpatternmatchingmayrequireappl

The method of obtaining the current date and time in SQL varies from database system. The common methods are as follows: 1. MySQL and MariaDB use NOW() or CURRENT_TIMESTAMP, which can be used to query, insert and set default values; 2. PostgreSQL uses NOW(), which can also use CURRENT_TIMESTAMP or type conversion to remove time zones; 3. SQLServer uses GETDATE() or SYSDATETIME(), which supports insert and default value settings; 4. Oracle uses SYSDATE or SYSTIMESTAMP, and pay attention to date format conversion. Mastering these functions allows you to flexibly process time correlations in different databases

The DISTINCT keyword is used in SQL to remove duplicate rows in query results. Its core function is to ensure that each row of data returned is unique and is suitable for obtaining a list of unique values ??for a single column or multiple columns, such as department, status or name. When using it, please note that DISTINCT acts on the entire row rather than a single column, and when used in combination with multiple columns, it returns a unique combination of all columns. The basic syntax is SELECTDISTINCTcolumn_nameFROMtable_name, which can be applied to single column or multiple column queries. Pay attention to its performance impact when using it, especially on large data sets that require sorting or hashing operations. Common misunderstandings include the mistaken belief that DISTINCT is only used for single columns and abused in scenarios where there is no need to deduplicate D

OLTPisidealforreal-timetransactions,whileOLAPissuitedforanalyzinglargedatavolumes.1)OLTPensuresdataintegrityforsystemslikee-commerce.2)OLAPexcelsinbusinessintelligenceforstrategicinsights.
