Exploring SQL Server 2022’s Enhanced Support for Ordered Data in Window Functions

SQL Server 2022 has brought several exciting enhancements, especially for window functions. These improvements make it easier to work with ordered data, a common requirement in many business scenarios. In this blog, we will explore these new features using the JBDB database. We’ll start with a detailed business use case and demonstrate the improvements with practical T-SQL queries. Let’s dive in! ๐ŸŒŠ

Business Use Case: Sales Performance Analysis ๐Ÿ“Š

Imagine a company, JB Enterprises, which needs to analyze the sales performance of its sales representatives over time. The goal is to:

  1. Rank sales representatives based on their monthly sales.
  2. Calculate the running total of sales for each representative.
  3. Determine the difference in sales between the current month and the previous month.

To achieve this, we’ll use SQL Server 2022’s enhanced window functions.

Setting Up the JBDB Database ๐Ÿ› ๏ธ

First, let’s set up our JBDB database and create the necessary tables:

-- Create the JBDB database
CREATE DATABASE JBDB;
GO

-- Use the JBDB database
USE JBDB;
GO

-- Create the Sales table
CREATE TABLE Sales (
    SalesID INT PRIMARY KEY IDENTITY,
    SalesRepID INT,
    SalesRepName NVARCHAR(100),
    SaleDate DATE,
    SaleAmount DECIMAL(10, 2)
);
GO

Now, let’s populate the Sales table with some sample data:

-- Insert sample data into the Sales table
INSERT INTO Sales (SalesRepID, SalesRepName, SaleDate, SaleAmount) VALUES
(1, 'Alice', '2023-01-15', 1000.00),
(1, 'Alice', '2023-02-15', 1500.00),
(1, 'Alice', '2023-03-15', 1200.00),
(2, 'Bob', '2023-01-20', 800.00),
(2, 'Bob', '2023-02-20', 1600.00),
(2, 'Bob', '2023-03-20', 1100.00),
(3, 'Charlie', '2023-01-25', 1300.00),
(3, 'Charlie', '2023-02-25', 1700.00),
(3, 'Charlie', '2023-03-25', 1800.00);
GO

Improved Support for Ordered Data in Window Functions ๐ŸŒŸ

SQL Server 2022 introduces several enhancements to window functions, making it easier to work with ordered data. Let’s explore these improvements with our use case.

1. Ranking Sales Representatives ๐Ÿ†

To rank sales representatives based on their monthly sales, we can use the RANK() function:

-- Rank sales representatives based on monthly sales
SELECT 
    SalesRepName,
    SaleDate,
    SaleAmount,
    RANK() OVER (PARTITION BY DATEPART(YEAR, SaleDate), DATEPART(MONTH, SaleDate) 
                 ORDER BY SaleAmount DESC) AS SalesRank
FROM 
    Sales
ORDER BY 
    SaleDate, SalesRank;

This query partitions the data by year and month and ranks the sales representatives within each partition based on their sales amount.

2. Calculating Running Total ๐Ÿงฎ

To calculate the running total of sales for each representative, we can use the SUM() function with the ROWS BETWEEN clause:

-- Calculate running total of sales for each representative
SELECT 
    SalesRepName,
    SaleDate,
    SaleAmount,
    SUM(SaleAmount) OVER (PARTITION BY SalesRepID ORDER BY SaleDate 
                          ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW) AS RunningTotal
FROM 
    Sales
ORDER BY 
    SalesRepName, SaleDate;

This query calculates the running total of sales for each representative, ordered by the sale date.

3. Calculating Month-over-Month Difference ๐Ÿ“‰๐Ÿ“ˆ

To determine the difference in sales between the current month and the previous month, we can use the LAG() function:

-- Calculate month-over-month difference in sales
SELECT 
    SalesRepName,
    SaleDate,
    SaleAmount,
    SaleAmount - LAG(SaleAmount, 1, 0) OVER (PARTITION BY SalesRepID ORDER BY SaleDate) AS MonthOverMonthDifference
FROM 
    Sales
ORDER BY 
    SalesRepName, SaleDate;

This query calculates the difference in sales between the current month and the previous month for each sales representative.

4. Average Monthly Sales per Representative ๐Ÿ“Š

To calculate the average monthly sales for each representative:

-- Calculate average monthly sales for each representative
SELECT 
    SalesRepName,
    DATEPART(YEAR, SaleDate) AS SaleYear,
    DATEPART(MONTH, SaleDate) AS SaleMonth,
    AVG(SaleAmount) OVER (PARTITION BY SalesRepID, DATEPART(YEAR, SaleDate), DATEPART(MONTH, SaleDate)) AS AvgMonthlySales
FROM 
    Sales
ORDER BY 
    SalesRepName, SaleYear, SaleMonth;

5. Cumulative Distribution of Sales ๐Ÿ“ˆ

To compute the cumulative distribution of sales amounts within each month:

-- Calculate cumulative distribution of sales within each month
SELECT 
    SalesRepName,
    SaleDate,
    SaleAmount,
    CUME_DIST() OVER (PARTITION BY DATEPART(YEAR, SaleDate), DATEPART(MONTH, SaleDate) 
                      ORDER BY SaleAmount) AS CumulativeDistribution
FROM 
    Sales
ORDER BY 
    SaleDate, SaleAmount;

6. Percentage Rank of Sales Representatives ๐ŸŽฏ

To assign a percentage rank to sales representatives based on their sales amounts:

-- Calculate percentage rank of sales representatives
SELECT 
    SalesRepName,
    SaleDate,
    SaleAmount,
    PERCENT_RANK() OVER (PARTITION BY DATEPART(YEAR, SaleDate), DATEPART(MONTH, SaleDate) 
                         ORDER BY SaleAmount) AS PercentageRank
FROM 
    Sales
ORDER BY 
    SaleDate, PercentageRank;

7. NTILE Function to Divide Sales into Quartiles ๐Ÿชœ

To divide sales amounts into quartiles for better distribution analysis:

-- Divide sales into quartiles
SELECT 
    SalesRepName,
    SaleDate,
    SaleAmount,
    NTILE(4) OVER (PARTITION BY DATEPART(YEAR, SaleDate), DATEPART(MONTH, SaleDate) 
                   ORDER BY SaleAmount) AS SalesQuartile
FROM 
    Sales
ORDER BY 
    SaleDate, SalesQuartile;

8. Median Sale Amount per Month ๐Ÿ“

To calculate the median sale amount for each month using the PERCENTILE_CONT function:

-- Calculate median sale amount per month
SELECT DISTINCT
    DATEPART(YEAR, SaleDate) AS SaleYear,
    DATEPART(MONTH, SaleDate) AS SaleMonth,
    PERCENTILE_CONT(0.5) WITHIN GROUP (ORDER BY SaleAmount) OVER (PARTITION BY DATEPART(YEAR, SaleDate), DATEPART(MONTH, SaleDate)) AS MedianSaleAmount
FROM 
    Sales
ORDER BY 
    SaleYear, SaleMonth;

9. Lead Function to Compare Next Month Sales ๐Ÿ“…

To compare the sales amount with the sales of the next month:

-- Compare sales amount with next month's sales
SELECT 
    SalesRepName,
    SaleDate,
    SaleAmount,
    LEAD(SaleAmount, 1, 0) OVER (PARTITION BY SalesRepID ORDER BY SaleDate) AS NextMonthSales,
    LEAD(SaleAmount, 1, 0) OVER (PARTITION BY SalesRepID ORDER BY SaleDate) - SaleAmount AS SalesDifference
FROM 
    Sales
ORDER BY 
    SalesRepName, SaleDate;

Conclusion ๐ŸŽ‰

SQL Server 2022’s enhanced support for ordered data in window functions provides powerful tools for analyzing and manipulating data. In this blog, we demonstrated how to use these improvements to rank sales representatives, calculate running totals, and determine month-over-month sales differences.

These enhancements simplify complex queries and improve performance, making it easier to gain insights from your data. Whether you’re analyzing sales performance or tackling other business challenges, SQL Server 2022’s window functions can help you achieve your goals more efficiently. ๐ŸŒŸ

Happy querying! ๐Ÿ’ป

For more tutorials and tips on  SQL Server, including performance tuning and  database management, be sure to check out our JBSWiki YouTube channel.

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided โ€œAS ISโ€ with no warranties, and confers no rights.

SQL Server 2022 STRING_SPLIT Enhancements: A Deep Dive with JBDB Database

In SQL Server 2022, the STRING_SPLIT function has been enhanced, making it a powerful tool for parsing and handling delimited strings. This blog will provide an exhaustive overview of these enhancements, using the JBDB database for demonstrations. We’ll explore a detailed business use case, delve into the new features, and provide T-SQL queries for you to practice and master the updated STRING_SPLIT function. Let’s dive in! ๐ŸŒŠ


Business Use Case: Customer Preferences Analysis ๐Ÿ›๏ธ

Imagine you’re working for an e-commerce company that tracks customer preferences for various product categories. Each customer’s preference is stored as a comma-separated string in the database. Your task is to analyze these preferences to offer personalized recommendations and optimize the marketing strategy.

For instance, the data might look like this:

  • Customer 1: Electronics,Books,Toys
  • Customer 2: Groceries,Fashion,Electronics
  • Customer 3: Books,Beauty,Fashion

With the enhancements in STRING_SPLIT in SQL Server 2022, you can efficiently parse these strings and analyze the data. Let’s explore how!


STRING_SPLIT Enhancements in SQL Server 2022 ๐Ÿš€

In SQL Server 2022, STRING_SPLIT has been enhanced to include:

  1. Ordinal Output: A new parameter, ordinal, can now be specified to include the position of each substring in the original string.
  2. Improved Performance: Enhanced indexing capabilities for better performance in large datasets.

Syntax:

STRING_SPLIT ( string, separator [, enable_ordinal ] )
  • string: The input string to be split.
  • separator: The delimiter character.
  • enable_ordinal: Optional; specifies whether to include the ordinal position of each substring (0 or 1).

Example 1: Basic Usage ๐ŸŒŸ

Let’s start with a simple example to see the new ordinal feature in action.

Setup:

USE JBDB;
GO

CREATE TABLE CustomerPreferences (
    CustomerID INT PRIMARY KEY,
    Preferences VARCHAR(100)
);

INSERT INTO CustomerPreferences (CustomerID, Preferences)
VALUES
(1, 'Electronics,Books,Toys'),
(2, 'Groceries,Fashion,Electronics'),
(3, 'Books,Beauty,Fashion');
GO

Query with STRING_SPLIT:

SELECT CustomerID, value, ordinal
FROM CustomerPreferences
CROSS APPLY STRING_SPLIT(Preferences, ',', 1);

This output shows the customer preferences along with their order of appearance. The ordinal column is a new addition in SQL Server 2022, providing valuable information about the sequence of items.

Example 2: Analyzing Preferences ๐Ÿ”

Now, let’s say we want to find out the most popular categories among all customers.

Query to Find Most Popular Categories:

SELECT value AS Category, COUNT(*) AS Count
FROM CustomerPreferences
CROSS APPLY STRING_SPLIT(Preferences, ',', 1)
GROUP BY value
ORDER BY Count DESC;

From the output, we can see that ‘Electronics’, ‘Books’, and ‘Fashion’ are the most popular categories. This data can be used to tailor marketing campaigns and inventory management.

Extracting Categories Based on Position:

  • Find customers whose second preference is ‘Fashion’:
SELECT CustomerID
FROM CustomerPreferences
CROSS APPLY STRING_SPLIT(Preferences, ',', 1)
WHERE ordinal = 2 AND value = 'Fashion';

Counting Unique Categories:

  • Count the number of unique categories preferred by customers:
SELECT COUNT(DISTINCT value) AS UniqueCategories
FROM CustomerPreferences
CROSS APPLY STRING_SPLIT(Preferences, ',', 1);

Combining STRING_SPLIT with Other Functions:

  • Find the length of each preference category string:
SELECT CustomerID, value, LEN(value) AS Length
FROM CustomerPreferences
CROSS APPLY STRING_SPLIT(Preferences, ',', 1);

Analyzing Preferences by Customer:

  • Count the number of preferences each customer has:
SELECT CustomerID, COUNT(*) AS PreferenceCount
FROM CustomerPreferences
CROSS APPLY STRING_SPLIT(Preferences, ',', 1)
GROUP BY CustomerID;

Extracting Values by Ordinal Position:

  • Identify customers whose first preference is ‘Electronics’:
SELECT CustomerID
FROM CustomerPreferences
CROSS APPLY STRING_SPLIT(Preferences, ',', 1)
WHERE ordinal = 1 AND value = 'Electronics';

Finding Specific Ordinal Positions:

  • Retrieve all customers whose third preference includes ‘Books’:
SELECT CustomerID
FROM CustomerPreferences
CROSS APPLY STRING_SPLIT(Preferences, ',', 1)
WHERE ordinal = 3 AND value = 'Books';

Filtering Based on Multiple Conditions:

  • Find customers who have ‘Books’ in any position and ‘Fashion’ as the last preference:
SELECT CustomerID
FROM CustomerPreferences
CROSS APPLY STRING_SPLIT(Preferences, ',', 1)
GROUP BY CustomerID
HAVING SUM(CASE WHEN value = 'Books' THEN 1 ELSE 0 END) > 0
   AND MAX(CASE WHEN value = 'Fashion' THEN ordinal ELSE 0 END) = COUNT(*);

Analyzing Distribution of Preferences:

  • Determine the number of customers who have each category as their first preference:
SELECT value AS FirstPreference, COUNT(*) AS Count
FROM CustomerPreferences
CROSS APPLY STRING_SPLIT(Preferences, ',', 1)
WHERE ordinal = 1
GROUP BY value
ORDER BY Count DESC;

Combining STRING_SPLIT with String Functions:

  • Find the customers with the longest category name in their preferences:
SELECT CustomerID, value, LEN(value) AS Length
FROM CustomerPreferences
CROSS APPLY STRING_SPLIT(Preferences, ',', 1)
ORDER BY Length DESC;

Using STRING_SPLIT for Data Transformation:

  • Convert customer preferences into a single concatenated string with a different delimiter:
SELECT CustomerID, STRING_AGG(value, '|') AS ConcatenatedPreferences
FROM CustomerPreferences
CROSS APPLY STRING_SPLIT(Preferences, ',', 1)
GROUP BY CustomerID;

Analyzing Preference Patterns:

  • Find the most common pattern of the first two preferences:
WITH FirstTwoPreferences AS (
    SELECT CustomerID, STRING_AGG(value, ',') WITHIN GROUP (ORDER BY ordinal) AS Pattern
    FROM CustomerPreferences
    CROSS APPLY STRING_SPLIT(Preferences, ',', 1)
    WHERE ordinal <= 2
    GROUP BY CustomerID
)
SELECT Pattern, COUNT(*) AS Count
FROM FirstTwoPreferences
GROUP BY Pattern
ORDER BY Count DESC;

Conclusion ๐Ÿ

The enhancements in SQL Server 2022’s STRING_SPLIT function, particularly the introduction of the ordinal parameter, provide powerful tools for handling and analyzing delimited strings. Whether you’re working with customer data, logs, or any form of delimited information, these enhancements can streamline your processes and deliver valuable insights.

Happy querying! ๐Ÿ˜„

For more tutorials and tips on SQL Server, including performance tuning and database management, be sure to check out our JBSWiki YouTube channel.

Thank You,
Vivek Janakiraman

Disclaimer:
The views expressed on this blog are mine alone and do not reflect the views of my company or anyone else. All postings on this blog are provided โ€œAS ISโ€ with no warranties, and confers no rights.