SQL Server 2022 UTF-8 Support Enhancements in Collation

In SQL Server 2022, UTF-8 support has been enhanced, offering more efficient storage and better performance for text data. This blog will explore these enhancements using the JBDB database and provide a detailed business use case to illustrate the benefits of adopting UTF-8 collation.

🌍Business Use Case: International E-commerce Platform 🌍

Imagine an international e-commerce platform that serves customers worldwide, offering products in multiple languages. The database needs to handle diverse character sets efficiently, from English to Japanese, Arabic, and more. Previously, using Unicode (UTF-16) required more storage space, leading to increased costs and slower performance. With SQL Server 2022’s improved UTF-8 support, the platform can now store multilingual text data more compactly, reducing storage costs and enhancing query performance.

UTF-8 Support in SQL Server 2022

SQL Server 2019 introduced UTF-8 as a new encoding option, allowing for more efficient storage of character data. SQL Server 2022 builds on this foundation by enhancing collation support, making it easier to work with UTF-8 encoded data. Let’s explore these enhancements using the JBDB database.

Setting Up the JBDB Database

First, we’ll set up the JBDB database and create a table to store product information in multiple languages.

CREATE DATABASE JBDB;
GO

USE JBDB;
GO

CREATE TABLE Products (
    ProductID INT PRIMARY KEY,
    ProductName NVARCHAR(100),
    ProductDescription NVARCHAR(1000),
    ProductDescription_UTF8 VARCHAR(1000) COLLATE Latin1_General_100_BIN2_UTF8
);
GO

In this example, ProductDescription uses the traditional NVARCHAR data type with UTF-16 encoding, while ProductDescription_UTF8 uses VARCHAR with the Latin1_General_100_BIN2_UTF8 collation for UTF-8 encoding.

Inserting Data with UTF-8 Collation πŸš€

Let’s insert some sample data into the Products table, showcasing different languages.

INSERT INTO Products (ProductID, ProductName, ProductDescription, ProductDescription_UTF8)
VALUES
(1, 'Laptop', N'ι«˜ζ€§θƒ½γƒŽγƒΌγƒˆγƒ‘γ‚½γ‚³γƒ³', 'ι«˜ζ€§θƒ½γƒŽγƒΌγƒˆγƒ‘γ‚½γ‚³γƒ³'), -- Japanese
(2, 'Smartphone', N'Ψ§Ω„Ω‡Ψ§Ψͺف Ψ§Ω„Ψ°ΩƒΩŠ Ψ§Ω„Ψ£ΩƒΨ«Ψ± ΨͺΩ‚Ψ―Ω…Ω‹Ψ§', 'Ψ§Ω„Ω‡Ψ§Ψͺف Ψ§Ω„Ψ°ΩƒΩŠ Ψ§Ω„Ψ£ΩƒΨ«Ψ± ΨͺΩ‚Ψ―Ω…Ω‹Ψ§'), -- Arabic
(3, 'Tablet', N'Nueva tableta con caracterΓ­sticas avanzadas', 'Nueva tableta con caracterΓ­sticas avanzadas'); -- Spanish
GO

Here, we use N'...' to denote Unicode literals for the NVARCHAR column and regular string literals for the VARCHAR column with UTF-8 encoding.

Querying and Comparing Storage Size πŸ“Š

To see the benefits of UTF-8 encoding, we’ll compare the storage size of the ProductDescription and ProductDescription_UTF8 columns.

SELECT
    ProductID,
    DATALENGTH(ProductDescription) AS UnicodeStorage,
    DATALENGTH(ProductDescription_UTF8) AS UTF8Storage
FROM Products;
GO

This query returns the number of bytes used to store each product description, illustrating the storage savings with UTF-8.

Working with UTF-8 Data πŸ”

Let’s perform some queries and operations on the UTF-8 encoded data.

Searching for Products in Japanese:

SELECT ProductID, ProductName, ProductDescription_UTF8
FROM Products
WHERE ProductDescription_UTF8 LIKE '%γƒŽγƒΌγƒˆγƒ‘γ‚½γ‚³γƒ³%';
GO

Updating UTF-8 Data:

UPDATE Products
SET ProductDescription_UTF8 = 'ι«˜ζ€§θƒ½γͺγƒŽγƒΌγƒˆγƒ‘γ‚½γ‚³γƒ³'
WHERE ProductID = 1;
GO

Ordering Data with UTF-8 Collation:

SELECT ProductID, ProductName, ProductDescription_UTF8
FROM Products
ORDER BY ProductDescription_UTF8 COLLATE Latin1_General_100_BIN2_UTF8;
GO

Advantages of UTF-8 in SQL Server 2022 πŸ†

  1. Reduced Storage Costs: UTF-8 encoding is more space-efficient than UTF-16, especially for languages using the Latin alphabet.
  2. Improved Performance: Smaller data size leads to faster reads and writes, enhancing overall performance.
  3. Enhanced Compatibility: UTF-8 is a widely-used encoding standard, making it easier to integrate with other systems and technologies.

Conclusion ✨

SQL Server 2022’s enhanced UTF-8 support in collation offers significant advantages for businesses dealing with multilingual data. By leveraging these enhancements, the international e-commerce platform in our use case can optimize storage, improve performance, and provide a seamless user experience across diverse languages.

Whether you’re dealing with global customer data or localized content, adopting UTF-8 collation in SQL Server 2022 can be a game-changer for your database management strategy.

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.

Enabling Azure Arc for SQL Server 2022: A Step-by-Step Guide

Enabling Azure Arc for SQL Server 2022 involves several key steps, including preparing your environment, registering your SQL Server instances, and managing them through the Azure portal.

Step 1: Prepare Your Environment

Before you can enable Azure Arc, ensure that your environment meets the following prerequisites:

  • Azure Subscription: You must have an active Azure subscription. If you don’t have one, you can sign up for a free account.
  • SQL Server 2022 Installation: Ensure that SQL Server 2022 is installed and configured on your on-premises or cloud infrastructure.
  • Azure CLI and Azure Connected Machine Agent: Install the Azure CLI on your management machine and the Azure Connected Machine Agent on the machines running SQL Server. These tools are necessary for managing resources via Azure Arc.

Installing Azure CLI

To install Azure CLI, use the following commands:

curl -sL https://aka.ms/InstallAzureCLIDeb | sudo bash

Installing Azure Connected Machine Agent

The Connected Machine Agent can be downloaded and installed as follows:

  • For Linux:
wget https://aka.ms/azcmagent -O ~/azcmagent.deb
sudo dpkg -i ~/azcmagent.deb

Step 2: Register SQL Server with Azure Arc

After setting up your environment, the next step is to connect your SQL Server instances to Azure Arc.

Connect Your Server

Login to Azure: Use the Azure CLI to log in to your Azure account.

    az login

    Connect the Machine: Register your on-premises SQL Server instance with Azure Arc.

    az cmagent connect --resource-group <ResourceGroupName> --tenant-id <TenantID> --location <Location> --subscription-id <SubscriptionID>

    Configure SQL Server Instance: After connecting the machine, configure the SQL Server instance for management under Azure Arc.

    az sql mi-arc create --resource-group <ResourceGroupName> --name <ManagedInstanceName> --location <Location> --admin-user <AdminUsername> --admin-password <AdminPassword>

    Step 3: Managing Your Arc-Enabled SQL Server

    Once your SQL Server instances are connected to Azure Arc, you can manage them through the Azure portal. This includes setting up monitoring, applying security and compliance policies, and leveraging advanced features like Azure Policy and Azure Security Center.

    Monitoring and Performance Management

    Use Azure Monitor to track the performance of your SQL Server instances. You can set up alerts for key performance metrics, such as CPU usage, memory consumption, and disk I/O.

    az monitor metrics alert create --name 'HighCPUAlert' --resource-group '<ResourceGroupName>' --scopes '/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Sql/servers/<ServerName>' --condition "avg Percentage CPU > 80" --description 'Alert for high CPU usage'

    Security and Compliance

    Implement security policies using Azure Policy to ensure your SQL Server instances comply with organizational standards. You can create custom policies or use built-in ones to enforce configurations like encrypted connections or secure authentication methods.

    az policy assignment create --name 'RequireSecureTransfer' --policy-definition '/subscriptions/<SubscriptionID>/providers/Microsoft.Authorization/policyDefinitions/<PolicyDefinitionID>' --scope '/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>'

    πŸ’Ό Business Use Case: Hybrid Cloud Strategy for a Global Retailer

    Company Profile

    A multinational retail corporation operates a complex IT infrastructure that includes on-premises data centers, public cloud environments, and edge devices deployed in stores worldwide. The company’s data management needs include real-time analytics, compliance with international data regulations, and secure data transfer across all environments.

    Challenges

    1. Diverse Environments: Managing data across various infrastructures, including on-premises, public cloud, and edge locations.
    2. Regulatory Compliance: Ensuring data security and compliance with regulations such as GDPR, CCPA, and PCI-DSS.
    3. Real-Time Analytics: Providing real-time insights to support business decisions and improve customer experience.
    4. Operational Efficiency: Reducing the complexity and cost of managing a global IT infrastructure.

    Solution: Azure Arc-Enabled SQL Server 2022

    The company implemented Azure Arc-enabled SQL Server 2022 to achieve a unified management and governance model for their data estate. This solution provided:

    • Centralized Management: The ability to manage all SQL Server instances from the Azure portal, regardless of their location.
    • Enhanced Security: Using Azure Security Center and Azure Policy to enforce consistent security and compliance policies across all environments.
    • Scalability: The flexibility to scale databases on-demand, optimizing resources and costs.
    • Real-Time Data Processing: Utilizing Azure Arc-enabled SQL Managed Instance features to deliver real-time analytics and insights.

    Benefits

    • Improved Operational Efficiency: Centralized management reduced administrative overhead and streamlined operations.
    • Enhanced Security and Compliance: Consistent security policies and compliance with international regulations protected sensitive data.
    • Scalability and Flexibility: The ability to scale resources based on demand ensured optimal performance and cost-efficiency.
    • Real-Time Insights: Real-time analytics capabilities improved customer experience and supported data-driven decision-making.

    πŸ“Š Practical Examples and Implementations

    Example 1: Enforcing Compliance with Azure Policy

    The retail company needed to ensure all SQL Server instances complied with PCI-DSS requirements. Using Azure Policy, they enforced encryption at rest and in transit across all databases.

    az policy assignment create --name 'EncryptionAtRest' --policy-definition '/subscriptions/<SubscriptionID>/providers/Microsoft.Authorization/policyDefinitions/<PolicyDefinitionID>' --scope '/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>'

    Example 2: Setting Up Real-Time Performance Monitoring

    To maintain optimal performance across their global SQL Server instances, the company set up real-time monitoring using Azure Monitor. They configured alerts for critical metrics like CPU utilization, memory usage, and disk I/O, enabling proactive issue resolution.

    az monitor metrics alert create --name 'DiskIOAlert' --resource-group '<ResourceGroupName>' --scopes '/subscriptions/<SubscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Sql/servers/<ServerName>' --condition "avg Disk I/O > 75" --description 'Alert for high disk I/O usage'

    πŸš€ Conclusion

    SQL Server 2022’s integration with Azure Arc represents a significant advancement in hybrid and multi-cloud data management. By leveraging Azure Arc, organizations can centralize management, enhance security, and ensure consistent performance across their entire data estate. Whether you’re managing data on-premises, in the cloud, or at the edge, Azure Arc-enabled SQL Server 2022 provides a powerful, flexible, and secure solution.

    For organizations like the global retailer in our case study, this integration not only simplifies operations but also delivers real-time insights, enhances security, and ensures compliance with international standards. As businesses continue to adopt hybrid cloud strategies, the capabilities provided by SQL Server 2022 and Azure Arc will be instrumental in achieving operational excellence and strategic agility.

    Embrace the future of data management with SQL Server 2022 and Azure Arc, and unlock the potential of your data estate! 🌟

    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.