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: Improved Performance for String Splitting and Parsing

In SQL Server 2022, Microsoft has introduced significant improvements in string splitting and parsing capabilities, making data manipulation more efficient. This blog explores these enhancements, providing practical examples using the JBDB database, and highlights a business use case to demonstrate the impact of these features.


📊 Business Use Case: Streamlining Data Analysis

Scenario:

A retail company, “TechShop,” collects customer feedback via online surveys. The responses are stored in a SQL Server database, and each response includes a comma-separated list of keywords describing the customer’s experience. The company wants to analyze these keywords to identify trends and improve its services.

Challenge:

With the previous SQL Server versions, splitting these comma-separated strings into individual keywords for analysis was resource-intensive and time-consuming, especially with large datasets. The goal is to leverage SQL Server 2022’s improved string splitting and parsing features to streamline this process.

🛠️ Key Features and Enhancements

1. STRING_SPLIT with Ordering Support

SQL Server 2022 introduces ordering support for the STRING_SPLIT function, allowing users to retain the order of elements in the original string. This enhancement is crucial for analyses where the sequence of data is significant.

2. Improved Performance

The performance of string splitting operations has been optimized, reducing execution time and resource consumption. This is particularly beneficial for large-scale data processing.

3. Enhanced Parsing Functions

Enhanced parsing functions provide more robust error handling and compatibility with different data types, improving data quality and reducing manual data cleaning efforts.

🧩 Example Demonstration with JBDB Database

Let’s dive into some examples using the JBDB database to showcase these improvements.

Setting Up the JBDB Database

First, we’ll set up a table to store customer feedback:

CREATE TABLE CustomerFeedback (
    FeedbackID INT IDENTITY(1,1) PRIMARY KEY,
    FeedbackText NVARCHAR(MAX)
);

INSERT INTO CustomerFeedback (FeedbackText)
VALUES
('Great service, fast shipping, quality products'),
('Slow delivery, excellent customer support'),
('Fantastic prices, will shop again, good variety'),
('Quality products, quick response time, friendly staff');

CREATE TABLE LargeCustomerFeedback (
    FeedbackID INT IDENTITY(1,1) PRIMARY KEY,
    FeedbackText NVARCHAR(MAX)
);

INSERT INTO LargeCustomerFeedback (FeedbackText)
VALUES
('Great service, fast shipping, quality products'),
('Slow delivery, excellent customer support'),
('Fantastic prices, will shop again, good variety'),
('Quality products, quick response time, friendly staff')
,('Great service1, fast shipping1, quality products1'),
('Slow delivery1, excellent customer support1'),
('Fantastic prices1, will shop again1, good variety1'),
('Quality products1, quick response time1, friendly staff1')
,('Great service2, fast shipping2, quality products2'),
('Slow delivery2, excellent customer support2'),
('Fantastic prices2, will shop again2, good variety2'),
('Quality products2, quick response time2, friendly staff2')
,('Great service3, fast shipping3, quality products3'),
('Slow delivery3, excellent customer support3'),
('Fantastic prices3, will shop again3, good variety3'),
('Quality products3, quick response time3, friendly staff3');

Using STRING_SPLIT with Ordering Support

Previously, STRING_SPLIT did not guarantee the order of elements. In SQL Server 2022, you can specify the order of elements:

SELECT 
    FeedbackID,
    value AS Keyword
FROM 
    CustomerFeedback
    CROSS APPLY STRING_SPLIT(FeedbackText, ',', 1)
ORDER BY 
    FeedbackID, ordinal;

In this query:

  • FeedbackText is split into individual keywords.
  • The ordinal column (optional) provides the order of elements as they appear in the original string.

Improved Performance Demonstration

To demonstrate the performance improvements, let’s compare the execution times for splitting a large dataset in SQL Server 2022 vs. a previous version. For simplicity, assume we have a LargeCustomerFeedback table similar to CustomerFeedback but with millions of rows.

Example Query for Large Dataset

SELECT 
    FeedbackID,
    value AS Keyword
FROM 
    LargeCustomerFeedback
    CROSS APPLY STRING_SPLIT(FeedbackText, ',', 1)
ORDER BY 
    FeedbackID, ordinal;

In practice, SQL Server 2022 processes this operation significantly faster, showcasing its enhanced string handling capabilities.

Counting Keywords from Feedback

To analyze the frequency of keywords mentioned in customer feedback, you can use the following query:

SELECT 
    value AS Keyword,
    COUNT(*) AS Frequency
FROM 
    CustomerFeedback
    CROSS APPLY STRING_SPLIT(FeedbackText, ',', 1)
GROUP BY 
    value
ORDER BY 
    Frequency DESC;

This query splits the feedback text into keywords and counts their occurrences, helping identify common themes or issues mentioned by customers.

Filtering Feedback Containing Specific Keywords

If you want to filter feedback entries containing specific keywords, such as “quality,” you can use:

SELECT 
    FeedbackID,
    FeedbackText
FROM 
    CustomerFeedback
WHERE 
    EXISTS (
        SELECT 1
        FROM STRING_SPLIT(FeedbackText, ',', 1)
        WHERE value = 'quality'
    );

This query finds feedback entries that mention “quality,” allowing the analysis of customer sentiments regarding product quality.

Extracting Unique Keywords

To extract unique keywords from all feedback entries, use the following query:

SELECT DISTINCT 
    value AS UniqueKeyword
FROM 
    CustomerFeedback
    CROSS APPLY STRING_SPLIT(FeedbackText, ',', 1);

This query provides a list of all unique keywords, helping identify the range of topics covered in customer feedback.

📈 Business Impact

By leveraging SQL Server 2022’s improved string splitting and parsing features, TechShop can:

  1. Accelerate Data Processing: The company can quickly analyze large volumes of customer feedback, allowing for timely insights into customer sentiment and trends.
  2. Improve Data Accuracy: The new features reduce the need for manual data cleaning and error handling, ensuring more accurate analysis.
  3. Enhance Customer Experience: By understanding customer feedback more efficiently, TechShop can make informed decisions to improve its services, leading to higher customer satisfaction and retention.

🎉 Conclusion

SQL Server 2022’s advancements in string splitting and parsing offer substantial benefits for data-driven businesses. The enhancements in performance, ordering support, and robust error handling make it easier and faster to analyze complex datasets. For companies like TechShop, these features enable better customer insights and more agile decision-making.

💡 Tip: Always test these features with your specific data and workload to fully understand the performance benefits and implementation considerations.

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: IS [NOT] DISTINCT FROM Predicate

SQL Server 2022 introduces a new predicate, IS [NOT] DISTINCT FROM, which simplifies the comparison of nullable columns. This feature is a boon for developers who often struggle with the nuanced behavior of NULL values in SQL comparisons. In this blog, we’ll explore how this new predicate works, its benefits, and provide a detailed business use case to illustrate its practical application.

Business Use Case: Analyzing Customer Orders

Imagine a retail company, JB Retail, that maintains a database (JBDB) to track customer orders. The company wants to analyze orders to identify customers who have updated their email addresses. However, due to some data migration issues, there are instances where old and new email addresses might be stored as NULL values.

To accurately identify customers who have changed their email addresses (or those whose email addresses are currently NULL but were previously not NULL), the IS [NOT] DISTINCT FROM predicate becomes very useful. This new feature allows us to simplify the logic and handle NULL comparisons more gracefully.

Setting Up the JBDB Database

First, let’s create the JBDB database and set up a sample table CustomerOrders to illustrate our use case.

-- Create JBDB database
CREATE DATABASE JBDB;
GO

-- Use the JBDB database
USE JBDB;
GO

-- Create CustomerOrders table
CREATE TABLE CustomerOrders (
    OrderID INT PRIMARY KEY,
    CustomerID INT,
    OldEmail NVARCHAR(255),
    NewEmail NVARCHAR(255),
    OrderDate DATE
);
GO

-- Insert sample data into CustomerOrders
INSERT INTO CustomerOrders (OrderID, CustomerID, OldEmail, NewEmail, OrderDate)
VALUES
    (1, 101, 'old_email1@example.com', 'new_email1@example.com', '2024-01-15'),
    (2, 102, 'old_email2@example.com', NULL, '2024-02-20'),
    (3, 103, NULL, 'new_email3@example.com', '2024-03-05'),
    (4, 104, 'old_email4@example.com', 'old_email4@example.com', '2024-04-10'),
    (5, 105, NULL, NULL, '2024-05-12');
GO

Understanding IS [NOT] DISTINCT FROM Predicate 🧩

The IS DISTINCT FROM predicate compares two expressions and returns TRUE if they are distinct (i.e., not equal or one is NULL and the other is not). The IS NOT DISTINCT FROM predicate, on the other hand, returns TRUE if they are not distinct (i.e., equal or both are NULL).

This is particularly useful when dealing with nullable columns, as NULL values are traditionally not equal to anything, including themselves, in SQL. The new predicate addresses this challenge.

Example Queries

Finding Customers Who Have Updated Their Email Address

    SELECT CustomerID, OldEmail, NewEmail
    FROM CustomerOrders
    WHERE OldEmail IS DISTINCT FROM NewEmail;

    This query identifies customers whose email addresses have changed. The IS DISTINCT FROM predicate ensures that it catches cases where either the old or new email could be NULL.

    Finding Customers Whose Email Address Remains Unchanged

    SELECT CustomerID, OldEmail, NewEmail
    FROM CustomerOrders
    WHERE OldEmail IS NOT DISTINCT FROM NewEmail;

    This query retrieves customers whose email addresses have not changed, including cases where both old and new emails are NULL.

      Detailed Business Use Case 🎯

      Let’s dive deeper into how JB Retail can use these queries to improve their customer relationship management. The company plans to send personalized emails to customers whose email addresses have been updated, acknowledging the change and ensuring it was intentional.

      Business Workflow

      Identify Updated Emails: The company will first use the IS DISTINCT FROM query to extract a list of customers with updated emails.

      SELECT CustomerID, OldEmail, NewEmail
      FROM CustomerOrders
      WHERE OldEmail IS DISTINCT FROM NewEmail;
      1. This query helps them identify cases where:
        • The old email was NULL and the new email is not, indicating a new addition.
        • The new email was NULL and the old email is not, indicating a removal.
        • Both emails are different but not NULL, indicating an actual change.
      2. Personalized Communication: Once the list is prepared, JB Retail can use it to send personalized communication to these customers. This step ensures that customers are aware of the changes and can report if the change was not authorized.
      3. Customer Service Follow-up: For cases where both old and new emails are NULL, the company can follow up with these customers to update their contact information, ensuring they do not miss out on important communications.

      Find Customers with NULL Values in Either Old or New Email

      This query helps identify customers where either the old or new email address is NULL, but not both.

      SELECT CustomerID, OldEmail, NewEmail
      FROM CustomerOrders
      WHERE OldEmail IS DISTINCT FROM NewEmail
      AND (OldEmail IS NULL OR NewEmail IS NULL);

      List Orders with Same Email Address Before and After

      This query lists orders where the email address remained the same before and after, but takes NULL into account.

      SELECT OrderID, CustomerID, OldEmail, NewEmail
      FROM CustomerOrders
      WHERE OldEmail IS NOT DISTINCT FROM NewEmail
      AND (OldEmail IS NOT NULL AND NewEmail IS NOT NULL);

      Find Orders with NULL Emails in Both Old and New

      This query identifies orders where both the old and new email addresses are NULL.

      SELECT OrderID, CustomerID, OldEmail, NewEmail
      FROM CustomerOrders
      WHERE OldEmail IS NOT DISTINCT FROM NewEmail
      AND OldEmail IS NULL;

      Identify Changes Where Old Email is NULL and New Email is Not

      This query finds orders where the old email address was NULL and the new email address is not NULL.

      SELECT OrderID, CustomerID, OldEmail, NewEmail
      FROM CustomerOrders
      WHERE OldEmail IS DISTINCT FROM NewEmail
      AND OldEmail IS NULL
      AND NewEmail IS NOT NULL;

      Find Orders Where Both Emails are Different or Both are NULL

      This query lists orders where the old and new emails are either both different or both NULL.

      SELECT OrderID, CustomerID, OldEmail, NewEmail
      FROM CustomerOrders
      WHERE (OldEmail IS DISTINCT FROM NewEmail
      AND OldEmail IS NOT NULL AND NewEmail IS NOT NULL)
      OR (OldEmail IS NULL AND NewEmail IS NULL);

      These queries leverage the IS [NOT] DISTINCT FROM predicate to handle various scenarios involving NULL values, providing flexibility and clarity in managing data comparisons. Feel free to adapt these queries based on your specific needs!

      Conclusion 🏁

      The introduction of the IS [NOT] DISTINCT FROM predicate in SQL Server 2022 is a significant enhancement for database developers and administrators. It simplifies the handling of NULL values in comparisons, making queries more readable and efficient.

      In the case of JB Retail, this feature enables a more accurate and efficient way to handle email updates, ensuring that the company maintains accurate customer contact information and strengthens its customer relationship management processes.

      With these new tools at your disposal, handling NULL values in SQL Server has never been easier! 🎉

      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.