Tag Archives: SQL Server 2022 guide

Standard

Posted by

Posted on

August 29, 2024

Posted under

SQL Server 2022

Comments

Leave a comment

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.

Standard

Posted by

Posted on

August 24, 2024

Posted under

SQL Server 2022

Comments

Leave a comment

Exploring the APPROX_COUNT_DISTINCT Function in SQL Server 2022

With the release of SQL Server 2022, a range of powerful new functions has been introduced, including the APPROX_COUNT_DISTINCT function. This function provides a fast and memory-efficient way to estimate the number of unique values in a dataset, making it an invaluable tool for big data scenarios where traditional counting methods may be too slow or resource-intensive. In this blog, we will explore the APPROX_COUNT_DISTINCT function, using the JBDB database for practical demonstrations and providing a detailed business use case to illustrate its benefits. Let’s dive into the world of approximate distinct counts! 🎉

Business Use Case: E-commerce Customer Segmentation 📦

In an e-commerce business, understanding the diversity of customer behavior is crucial for personalized marketing and inventory management. The JBDB database contains customer transaction data, including CustomerID, ProductID, and PurchaseDate. The business aims to estimate the number of unique customers making purchases each month and the variety of products they are buying. Using the APPROX_COUNT_DISTINCT function, the company can quickly analyze this data to identify trends, optimize stock levels, and tailor marketing campaigns.

Understanding the APPROX_COUNT_DISTINCT Function 🧠

The APPROX_COUNT_DISTINCT function estimates the number of distinct values in a column, offering a performance-efficient alternative to the traditional COUNT(DISTINCT column) approach. It is particularly useful in large datasets where an exact count is less critical than performance and resource usage.

Syntax:

APPROX_COUNT_DISTINCT ( column_name )
  • column_name: The column from which distinct values are counted.

Example 1: Estimating Unique Customers per Month 📅

Let’s calculate the estimated number of unique customers making purchases each month in the JBDB database.

Setup:

USE JBDB;
GO

CREATE TABLE CustomerTransactions (
    TransactionID INT PRIMARY KEY,
    CustomerID INT,
    ProductID INT,
    PurchaseDate DATE
);

INSERT INTO CustomerTransactions (TransactionID, CustomerID, ProductID, PurchaseDate)
VALUES
(1, 101, 2001, '2023-01-05'),
(2, 102, 2002, '2023-01-10'),
(3, 101, 2003, '2023-01-15'),
(4, 103, 2001, '2023-02-05'),
(5, 104, 2002, '2023-02-10'),
(6, 102, 2004, '2023-02-15'),
(7, 105, 2005, '2023-03-05'),
(8, 106, 2001, '2023-03-10');
GO

Query to Estimate Unique Customers:

SELECT 
    FORMAT(PurchaseDate, 'yyyy-MM') AS Month,
    APPROX_COUNT_DISTINCT(CustomerID) AS EstimatedUniqueCustomers
FROM CustomerTransactions
GROUP BY FORMAT(PurchaseDate, 'yyyy-MM');

Output:

MonthEstimatedUniqueCustomers
2023-012
2023-023
2023-032

This output gives an approximate count of unique customers making purchases in each month, providing quick insights into customer engagement over time.

Example 2: Estimating Product Variety by Month 📊

Now, let’s estimate the variety of products purchased each month to understand product diversity and demand trends.

Query to Estimate Product Variety:

SELECT 
    FORMAT(PurchaseDate, 'yyyy-MM') AS Month,
    APPROX_COUNT_DISTINCT(ProductID) AS EstimatedUniqueProducts
FROM CustomerTransactions
GROUP BY FORMAT(PurchaseDate, 'yyyy-MM');

Output:

MonthEstimatedUniqueProducts
2023-013
2023-023
2023-032

This data helps the business understand which months had the highest product variety, aiding in inventory and supply chain management.

Example 3: Comparing Traditional and Approximate Counts 🔄

To illustrate the efficiency of APPROX_COUNT_DISTINCT, let’s compare it with the traditional COUNT(DISTINCT column) method.

Traditional COUNT(DISTINCT) Method:

SELECT 
    FORMAT(PurchaseDate, 'yyyy-MM') AS Month,
    COUNT(DISTINCT CustomerID) AS ExactUniqueCustomers
FROM CustomerTransactions
GROUP BY FORMAT(PurchaseDate, 'yyyy-MM');

Approximate COUNT(DISTINCT) Method:

SELECT 
    FORMAT(PurchaseDate, 'yyyy-MM') AS Month,
    APPROX_COUNT_DISTINCT(CustomerID) AS EstimatedUniqueCustomers
FROM CustomerTransactions
GROUP BY FORMAT(PurchaseDate, 'yyyy-MM');

Comparison:

MonthExactUniqueCustomersEstimatedUniqueCustomers
2023-0122
2023-0233
2023-0322

The approximate method provides similar results with potentially significant performance improvements, especially in large datasets.

Estimating Unique Products by Customer:

  • Calculate the estimated number of unique products purchased by each customer:
SELECT 
    CustomerID,
    APPROX_COUNT_DISTINCT(ProductID) AS EstimatedUniqueProducts
FROM CustomerTransactions
GROUP BY CustomerID;

Estimating Unique Purchase Dates:

  • Estimate the number of unique purchase dates in the dataset:
SELECT 
    APPROX_COUNT_DISTINCT(PurchaseDate) AS EstimatedUniquePurchaseDates
FROM CustomerTransactions;

Regional Sales Analysis:

  • If the dataset includes a region column, estimate unique customers per region:
SELECT 
    Region,
    APPROX_COUNT_DISTINCT(CustomerID) AS EstimatedUniqueCustomers
FROM CustomerTransactions
GROUP BY Region;

Conclusion 🏁

The APPROX_COUNT_DISTINCT function in SQL Server 2022 is a powerful tool for quickly estimating the number of distinct values in large datasets. This function is particularly useful in big data scenarios where performance and resource efficiency are crucial. By leveraging APPROX_COUNT_DISTINCT, businesses can gain rapid insights into customer behavior, product diversity, and other key metrics, enabling more informed decision-making. Whether you’re analyzing e-commerce data, customer segmentation, or product sales, this function offers a robust solution for your data analysis needs. 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.

Standard

Posted by

Posted on

August 23, 2024

Posted under

SQL Server 2022

Comments

Leave a comment

Exploring SQL Server 2022 APPROX_PERCENTILE_DISC Function with JBDB Database

SQL Server 2022 introduces several powerful features to enhance data analysis and performance. Among these, the APPROX_PERCENTILE_DISC function offers an efficient way to calculate discrete percentiles from large datasets. This blog will explore this function in depth, using practical examples from the JBDB database, and provide a detailed business use case to illustrate its utility. Let’s dive into the world of approximate discrete percentiles! 🎉

Business Use Case: Analyzing Customer Satisfaction 📊

Imagine a retail company seeking to understand customer satisfaction across different store locations. The data, stored in the JBDB database, includes satisfaction scores ranging from 1 to 5, representing customers’ overall experience. The company aims to identify key percentiles such as the median (50th percentile) and the 90th percentile to gauge typical and top-tier satisfaction levels. Using APPROX_PERCENTILE_DISC, they can efficiently compute these discrete percentiles, helping to guide strategies for improving customer experience and focusing on high-impact areas.

Understanding the APPROX_PERCENTILE_DISC Function 🧠

The APPROX_PERCENTILE_DISC function in SQL Server 2022 is designed to calculate approximate discrete percentiles from a sorted set of values. Unlike the continuous APPROX_PERCENTILE_CONT, this function returns the value nearest to the percentile rank, which is particularly useful for ordinal data.

Syntax:

APPROX_PERCENTILE_DISC ( percentile ) WITHIN GROUP ( ORDER BY column_name )
  • percentile: A numeric value between 0 and 1, indicating the desired percentile.
  • column_name: The column used to order the dataset before calculating the percentile.

Example 1: Calculating Key Percentiles 🔍

Let’s calculate the median (50th percentile) and 90th percentile of customer satisfaction scores.

Setup:

USE JBDB;
GO

CREATE TABLE CustomerSatisfaction (
    CustomerID INT PRIMARY KEY,
    StoreID INT,
    SatisfactionScore INT,
    ReviewDate DATE
);

INSERT INTO CustomerSatisfaction (CustomerID, StoreID, SatisfactionScore, ReviewDate)
VALUES
(1, 101, 5, '2023-01-15'),
(2, 102, 3, '2023-01-16'),
(3, 103, 4, '2023-01-17'),
(4, 101, 2, '2023-01-18'),
(5, 104, 5, '2023-01-19'),
(6, 105, 4, '2023-01-20'),
(7, 106, 3, '2023-01-21'),
(8, 102, 5, '2023-01-22');
GO

Query to Calculate 50th and 90th Percentiles:

SELECT 
    APPROX_PERCENTILE_DISC(0.50) WITHIN GROUP (ORDER BY SatisfactionScore) AS MedianScore,
    APPROX_PERCENTILE_DISC(0.90) WITHIN GROUP (ORDER BY SatisfactionScore) AS Top10PercentScore
FROM CustomerSatisfaction;

Output:

MedianScoreTop10PercentScore
45

This output reveals that the median satisfaction score is 4, and the top 10% of scores are 5, indicating a high level of satisfaction among the top-tier customers.

Example 2: Store-Level Satisfaction Analysis 🏪

Next, let’s analyze satisfaction scores at different store locations to identify trends and areas for improvement.

Query for Store-Level Analysis:

SELECT 
    StoreID,
    APPROX_PERCENTILE_DISC(0.50) WITHIN GROUP (ORDER BY SatisfactionScore) AS MedianScore,
    APPROX_PERCENTILE_DISC(0.90) WITHIN GROUP (ORDER BY SatisfactionScore) AS Top10PercentScore
FROM CustomerSatisfaction
GROUP BY StoreID;

Output:

StoreIDMedianScoreTop10PercentScore
10135
10245
10344
10455
10544
10633

This analysis helps identify which stores are excelling in customer satisfaction and which may need targeted improvements.

Example 3: Customer Segmentation by Satisfaction Levels 📈

To further analyze the data, let’s segment customers into different satisfaction levels based on key percentiles.

Step 1: Calculate Percentiles

-- Calculate the 25th, 50th, and 75th percentiles
SELECT 
    APPROX_PERCENTILE_DISC(0.25) WITHIN GROUP (ORDER BY SatisfactionScore) AS Q1,
    APPROX_PERCENTILE_DISC(0.50) WITHIN GROUP (ORDER BY SatisfactionScore) AS Q2,
    APPROX_PERCENTILE_DISC(0.75) WITHIN GROUP (ORDER BY SatisfactionScore) AS Q3
INTO #Percentiles
FROM CustomerSatisfaction;

Step 2: Segment Customers

-- Join with the Percentiles table to categorize customers
SELECT 
    cs.CustomerID,
    cs.SatisfactionScore,
    CASE 
        WHEN cs.SatisfactionScore <= p.Q1 THEN 'Low'
        WHEN cs.SatisfactionScore <= p.Q2 THEN 'Medium'
        WHEN cs.SatisfactionScore <= p.Q3 THEN 'High'
        ELSE 'Very High'
    END AS SatisfactionLevel
FROM 
    CustomerSatisfaction cs
CROSS JOIN 
    #Percentiles p;

Cleanup

-- Drop the temporary table
DROP TABLE #Percentiles;

Explanation:

  1. Calculate Percentiles:
    • The first step calculates the 25th (Q1), 50th (Q2), and 75th (Q3) percentiles and stores them in a temporary table #Percentiles.
  2. Segment Customers:
    • The second step uses these percentile values to categorize each customer’s satisfaction score into levels: ‘Low’, ‘Medium’, ‘High’, or ‘Very High’.
  3. Cleanup:
    • Finally, the temporary table #Percentiles is dropped to clean up the session.

Analyzing Low Satisfaction Scores:

  • Identify stores with the lowest 10th percentile satisfaction scores:
SELECT 
    StoreID,
    APPROX_PERCENTILE_DISC(0.10) WITHIN GROUP (ORDER BY SatisfactionScore) AS Low10PercentScore
FROM CustomerSatisfaction
GROUP BY StoreID;

Comparing Satisfaction Over Time:

  • Compare median satisfaction scores between two periods:
SELECT 
    'Period 1' AS Period,
    APPROX_PERCENTILE_DISC(0.50) WITHIN GROUP (ORDER BY SatisfactionScore) AS MedianScore
FROM CustomerSatisfaction
WHERE ReviewDate BETWEEN '2023-01-15' AND '2023-01-18'
UNION ALL
SELECT 
    'Period 2' AS Period,
    APPROX_PERCENTILE_DISC(0.50) WITHIN GROUP (ORDER BY SatisfactionScore) AS MedianScore
FROM CustomerSatisfaction
WHERE ReviewDate BETWEEN '2023-01-19' AND '2023-01-22';

3. Identifying High-Performing Stores:

  • List stores with a 90th percentile satisfaction score of 5:
SELECT StoreID
FROM CustomerSatisfaction
GROUP BY StoreID
HAVING APPROX_PERCENTILE_DISC(0.90) WITHIN GROUP (ORDER BY SatisfactionScore) = 5;

Conclusion 🏁

The APPROX_PERCENTILE_DISC function in SQL Server 2022 is a robust tool for efficiently estimating discrete percentiles. It offers a quick and practical solution for analyzing large datasets, making it invaluable for businesses looking to gain insights into customer behavior, product performance, and more. Whether you’re assessing customer satisfaction, analyzing sales data, or exploring other metrics, the APPROX_PERCENTILE_DISC function provides a clear and concise way to understand your data. 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.