Tag Archives: SQL Server Tutorials

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 28, 2024

Posted under

SQL Server 2022

Comments

Leave a comment

SQL Server 2022 TRY_CONVERT and TRY_CAST Enhancements

SQL Server 2022 introduces enhancements to the TRY_CONVERT and TRY_CAST functions, providing more robust and reliable data type conversions. These enhancements improve data integrity and reduce errors in data transformations, making them invaluable tools for database administrators and developers. In this blog, we’ll explore these enhancements using the JBDB database and provide a detailed business use case to demonstrate their practical applications.

📊 Business Use Case: Data Quality Assurance in Financial Reporting

In our fictional company, JB Financials, maintaining high data quality in financial reports is crucial. The company uses a wide range of data sources, including legacy systems that often provide data in inconsistent formats. Ensuring accurate data conversion without losing critical information is essential for financial accuracy.

JB Financials has a table, FinancialData, that stores various types of financial information, including amounts in different currencies, dates, and other numerical values. The challenge is to convert this data into standardized formats for reporting purposes, while gracefully handling any conversion errors.

📋 Table Schema: FinancialData

CREATE TABLE FinancialData (
    RecordID INT PRIMARY KEY,
    RawAmount VARCHAR(50),
    RawDate VARCHAR(50),
    CurrencyCode VARCHAR(10)
);

INSERT INTO FinancialData (RecordID, RawAmount, RawDate, CurrencyCode)
VALUES
(1, '1234.56', '2023-07-15', 'USD'),
(2, '1234,56', '15/07/2023', 'EUR'),
(3, '1,234.56', '07/15/2023', 'USD'),
(4, '1.234,56', '2023.07.15', 'JPY'),
(5, 'invalid', 'invalid', 'GBP');

🔄 TRY_CONVERT and TRY_CAST Enhancements

The TRY_CONVERT and TRY_CAST functions in SQL Server 2022 have been enhanced to provide better handling of data conversion scenarios, especially with cultural settings and invalid data. These functions attempt to convert expressions to the specified data type and return NULL if the conversion fails, without raising an error.

Example: TRY_CONVERT

The TRY_CONVERT function attempts to convert the provided expression to the specified data type.

SELECT 
    RecordID,
    RawAmount,
    TRY_CONVERT(DECIMAL(10, 2), RawAmount, 1) AS ConvertedAmount
FROM FinancialData;

This query attempts to convert the RawAmount values to DECIMAL(10, 2) with style 1 (for converting strings with commas). The enhanced TRY_CONVERT gracefully handles invalid conversions, such as ‘invalid’ in the data, returning NULL instead of raising an error.

Example: TRY_CAST

The TRY_CAST function is similar to TRY_CONVERT but provides a more straightforward syntax for simple conversions.

SELECT 
    RecordID,
    RawDate,
    TRY_CAST(RawDate AS DATE) AS ConvertedDate
FROM FinancialData;

This query attempts to cast the RawDate values to the DATE data type. The TRY_CAST function will return NULL for the ‘invalid’ date format, avoiding potential runtime errors.

📈 Detailed Business Use Case: Data Standardization for Financial Reports

Scenario: JB Financials needs to standardize and validate the data in the FinancialData table before generating monthly financial reports. This involves converting the raw amount data to a standardized currency format and converting date strings to a standard DATE format.

Solution:

  1. Standardizing Amounts: Use TRY_CONVERT to convert the RawAmount to a DECIMAL type, ensuring proper handling of different number formats (e.g., commas and periods).
  2. Validating Dates: Use TRY_CAST to convert the RawDate to a DATE type, handling various date formats and invalid data.
  3. Generating Reports: Use the converted data to generate accurate financial reports.

Implementation:

SELECT 
    RecordID,
    TRY_CONVERT(DECIMAL(10, 2), RawAmount, 1) AS StandardizedAmount,
    TRY_CAST(RawDate AS DATE) AS StandardizedDate,
    CurrencyCode
INTO FinancialReports
FROM FinancialData
WHERE TRY_CONVERT(DECIMAL(10, 2), RawAmount, 1) IS NOT NULL
AND TRY_CAST(RawDate AS DATE) IS NOT NULL;

This query creates a new table, FinancialReports, with standardized and validated data. Only rows with successfully converted amounts and dates are included, ensuring high data quality for the reports.

🎉 Conclusion

The TRY_CONVERT and TRY_CAST enhancements in SQL Server 2022 offer powerful tools for handling data type conversions, especially in scenarios with inconsistent or invalid data. By using these functions, JB Financials can standardize and validate their data, ensuring accurate and reliable financial reporting.

These enhancements reduce the risk of errors and improve the robustness of data transformation processes, making them essential for any organization dealing with diverse data sources and formats. Whether you’re handling financial data, customer information, or any other type of data, the TRY_CONVERT and TRY_CAST functions can help ensure that your data conversions are smooth and error-free.

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 26, 2024

Posted under

SQL Server 2022

Comments

Leave a comment

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.