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.

Automation and DevOps with SQL Server 2022: Integrating CI/CD and Automation Tools

In the modern development landscape, the integration of DevOps practices and automation is crucial for delivering high-quality software efficiently. SQL Server 2022 brings a host of new features and improvements that make it easier than ever to integrate database management into DevOps workflows. This blog post will explore how to leverage SQL Server 2022 in DevOps pipelines, focusing on Continuous Integration/Continuous Deployment (CI/CD) and automation tools.

๐Ÿš€ The Role of DevOps in Database Management

DevOps emphasizes collaboration between development and operations teams, aiming to deliver applications and services more efficiently. In the context of databases, DevOps practices help ensure that database changes are integrated, tested, and deployed as seamlessly as application code. Key benefits include:

  • Improved collaboration between developers and DBAs.
  • Faster delivery cycles through automated deployments.
  • Reduced risk with consistent and repeatable processes.

๐Ÿ› ๏ธ Setting Up CI/CD for SQL Server 2022

Continuous Integration (CI) and Continuous Deployment (CD) are fundamental components of a DevOps strategy. CI involves automatically integrating and testing code changes, while CD automates the deployment of these changes to production.

1. Database Version Control

Version control is a critical aspect of CI/CD. Tools like Git can be used to track changes to database schema and code. SQL Server 2022 works seamlessly with version control systems, allowing you to manage your database scripts (e.g., schema, stored procedures, functions) just like application code.

2. Automated Builds and Testing

Automating the build and testing process is crucial for catching issues early. Hereโ€™s how to set it up:

  • SQL Server Data Tools (SSDT): Use SSDT to create and manage database projects in Visual Studio. It allows you to define the database schema as code and includes tools for schema comparison and deployment.
  • Azure DevOps Pipelines: Azure DevOps provides robust CI/CD capabilities. You can define pipelines that automatically build your database project, run unit tests, and deploy changes. For example:
trigger:
  - main

pool:
  vmImage: 'windows-latest'

steps:
  - task: UseDotNet@2
    inputs:
      packageType: 'sdk'
      version: '3.x.x'

  - task: NuGetToolInstaller@1

  - task: NuGetCommand@2
    inputs:
      restoreSolution: '$(solution)'

  - task: VSBuild@1
    inputs:
      solution: '**/*.sln'
      msbuildArgs: '/p:DeployOnBuild=true /p:PublishProfile=$(publishProfile)'

  - task: PublishTestResults@2
    inputs:
      testRunner: 'VSTest'
      testResultsFiles: '**/*.trx'
  • Automated Testing: Incorporate automated tests to validate database changes. Use tools like tSQLt, a unit testing framework for T-SQL, to write and execute tests. This ensures that your changes do not introduce regressions.

3. Continuous Deployment

Continuous Deployment extends CI by automating the deployment of code changes to various environments, including staging and production.

  • Database Migration Tools: Tools like Flyway and Liquibase can automate database migrations, ensuring that schema changes are applied consistently across environments.
  • Release Management: Use release management tools like Octopus Deploy or Azure DevOps Release Pipelines to orchestrate deployments. These tools provide features like approvals, rollbacks, and environment-specific configurations.

โš™๏ธ Automation Tools in SQL Server 2022

SQL Server 2022 includes several features and integrations that facilitate automation:

1. SQL Server Agent

SQL Server Agent is a powerful job scheduling tool that can automate routine tasks, such as backups, index maintenance, and monitoring. You can integrate SQL Server Agent jobs into your CI/CD pipelines to automate post-deployment tasks.

2. PowerShell and dbatools

PowerShell is a versatile scripting language that can automate various SQL Server tasks. The dbatools module, in particular, provides a rich set of cmdlets for managing SQL Server instances, databases, and backups.

Example: Automating backup verification using dbatools:

Install-Module dbatools
Import-Module dbatools

$servers = "Server1", "Server2"
foreach ($server in $servers) {
    Test-DbaLastBackup -SqlInstance $server -Databases master, msdb, model
}

3. Azure Automation

Azure Automation allows you to automate management tasks using runbooks. For SQL Server, you can create runbooks to automate tasks like scaling, backup management, and monitoring.

๐ŸŒ Hybrid and Cloud Integration

SQL Server 2022 is designed with cloud and hybrid environments in mind, making it easier to manage and automate SQL Server across on-premises and cloud platforms. Key integrations include:

  • Azure Arc: Azure Arc-enabled data services allow you to manage SQL Server instances across different environments, providing a unified management experience.
  • Azure DevOps and GitHub Actions: These platforms provide cloud-native CI/CD solutions that integrate seamlessly with SQL Server, enabling automated deployments to Azure SQL Database, SQL Managed Instance, and on-premises SQL Server instances.

๐Ÿ”„ Best Practices for Database DevOps

  1. Treat Database Schema as Code: Use version control for database schema changes to maintain a history and enable collaboration.
  2. Automate Everything: From builds and tests to deployments and backups, automation reduces the risk of human error and ensures consistency.
  3. Implement Robust Testing: Use unit tests, integration tests, and automated testing frameworks to validate changes.
  4. Monitor Continuously: Use monitoring tools to track the performance and health of your databases, ensuring that any issues are detected early.
  5. Plan for Rollbacks: Always have a rollback plan in place in case of deployment failures. This might include database backups or transactional scripts.

๐Ÿš€ Conclusion

SQL Server 2022 brings powerful new features and integrations that make it an excellent choice for DevOps practices. By implementing CI/CD pipelines and automation tools, you can streamline database management, improve collaboration, and accelerate the delivery of high-quality software. Whether you’re working in a purely on-premises environment, in the cloud, or in a hybrid setup, SQL Server 2022 provides the flexibility and capabilities needed to succeed in today’s fast-paced development world.

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.

Comprehensive Guide to Monitoring SQL Server: Optimizing Max Server Memory

Monitoring a SQL Server database is essential to maintain its performance, stability, and overall health. One crucial aspect of SQL Server configuration is setting the max server memory value appropriately. This blog provides an in-depth look at how to monitor SQL Server and how to determine the best value for the max server memory setting, using various tools and methods.


๐Ÿ” Key Tools and Techniques for Monitoring SQL Server

Effective monitoring of a SQL Server environment involves multiple tools and techniques, each offering unique insights.

1. SQL Server Management Studio (SSMS)

SSMS provides built-in features for monitoring SQL Server:

  • Activity Monitor: A real-time interface that displays CPU usage, I/O statistics, recent expensive queries, and more.
  • Performance Dashboard Reports: Pre-defined reports that provide details on CPU, memory, and I/O usage.
2. Dynamic Management Views (DMVs)

DMVs allow querying internal SQL Server metrics:

  • sys.dm_os_performance_counters: Retrieves various performance counters, including memory usage.
  • sys.dm_exec_query_stats: Provides statistics on query performance.
  • sys.dm_os_sys_memory: Displays the amount of memory in use and available.
3. Extended Events

Extended Events provide a lightweight, flexible way to collect data on SQL Server events:

  • Configure sessions to capture specific data points, such as long-running queries or memory usage spikes.
4. SQL Server Profiler & Trace

Although deprecated, SQL Server Profiler can still be used for tracing events and diagnosing issues.

5. Performance Monitor (PerfMon)

PerfMon is a Windows utility that provides detailed insights into system and SQL Server performance. It allows tracking various counters, essential for understanding SQL Server’s memory usage.


๐Ÿ“ˆ Key Performance Monitor (PerfMon) Counters for SQL Server

Using PerfMon, you can monitor several critical counters that provide insight into SQL Server’s memory management and overall performance:

  1. Memory: Available MBytes
    • What it measures: The amount of physical memory available on the system.
    • Why it matters: Helps determine if the system has enough memory to support both SQL Server and other applications.
  2. SQLServer: Memory Manager – Total Server Memory (KB)
    • What it measures: The total amount of dynamic memory the SQL Server is using.
    • Why it matters: Indicates how much memory SQL Server is consuming and helps in understanding if the configured memory is adequate.
  3. SQLServer: Memory Manager – Target Server Memory (KB)
    • What it measures: The ideal amount of memory SQL Server aims to use.
    • Why it matters: Helps in determining if SQL Server is using less memory than needed, which could lead to performance issues.
  4. SQLServer: Buffer Manager – Buffer Cache Hit Ratio
    • What it measures: The percentage of pages found in the buffer cache without requiring a read from disk.
    • Why it matters: A high buffer cache hit ratio generally indicates that the SQL Server has sufficient memory allocated for caching.
  5. SQLServer: Buffer Manager – Page Life Expectancy
    • What it measures: The number of seconds a page will stay in the buffer cache.
    • Why it matters: A lower value indicates that pages are being flushed out too quickly, which may suggest the need for more memory.

๐Ÿงฎ Calculating the Optimal Max Server Memory Setting

To determine the optimal max server memory setting, consider the following steps:

1. Identify Total Physical Memory

Determine the total physical memory available on your server. For example, if your server has 64 GB of RAM, this is your baseline.

2. Reserve Memory for the OS and Other Applications

It’s crucial to leave enough memory for the OS and other applications. A common practice is to reserve around 20% of the total memory for the OS. For example, with 64 GB of RAM, you might reserve 12-16 GB for the OS, leaving 48-52 GB for SQL Server.

3. Use PerfMon Data to Fine-Tune

Using PerfMon, monitor the following:

  • Memory: Available MBytes: Ensure that this value does not drop too low, indicating a lack of available memory.
  • SQLServer: Memory Manager – Total Server Memory (KB) and Target Server Memory (KB): If Total Server Memory consistently meets or exceeds Target Server Memory, it may indicate a need for more memory.
  • SQLServer: Buffer Manager – Buffer Cache Hit Ratio: Aim for a ratio above 90%.
  • SQLServer: Buffer Manager – Page Life Expectancy: Aim for a value greater than 300 seconds.
4. Adjust Max Server Memory

After analyzing the data, adjust the max server memory setting using the following SQL command:

EXEC sp_configure 'max server memory', 49152; -- Example: Set to 48 GB
RECONFIGURE;
5. Regular Review and Adjustment

Regularly review your settings, especially after significant workload changes. As workloads evolve, memory requirements may change, necessitating adjustments to the max server memory setting.


๐Ÿš€ Conclusion

Effective monitoring and optimal memory configuration are key to maintaining SQL Server performance. By leveraging tools like SSMS, DMVs, Extended Events, and PerfMon, you can gain valuable insights into your SQL Server’s memory usage and overall performance. Setting the correct max server memory is crucial to ensure your SQL Server runs efficiently without starving the OS or other applications of necessary resources.

For more detailed tutorials and insights, be sure to check out our YouTube channel,ย JBSWiki YouTube channel, where we cover SQL Server and Azure SQL topics in depth.

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.