Tag Archives: SQL Server analysis tools

Standard

Posted by

Posted on

September 2, 2024

Posted under

SQL Server 2022

Comments

Leave a comment

Unleashing SQL Server 2022: Enhancements to sys.dm_exec_query_statistics_xml

In the world of data management and analysis, SQL Server 2022 has brought numerous improvements and enhancements, one of the most notable being the advancements to the dynamic management view (DMV) sys.dm_exec_query_statistics_xml. This DMV provides detailed runtime statistics about query execution, which is invaluable for performance tuning and query optimization.

In this blog, we will explore the enhancements to sys.dm_exec_query_statistics_xml in SQL Server 2022 using the JBDB database. We’ll walk through a comprehensive business use case, demonstrate these enhancements with T-SQL queries, and show how these can be leveraged for better performance insights.

Business Use Case: Optimizing an E-commerce Database 🛒

Imagine you are a database administrator for JBDB, an e-commerce platform with millions of users and transactions. Ensuring optimal query performance is crucial for providing a seamless user experience. You need to monitor query performance, identify slow-running queries, and understand execution patterns to make informed optimization decisions.

The JBDB Database Schema

For this demo, we’ll use a simplified version of the JBDB database with the following schema:

  • Customers: Stores customer information.
  • Orders: Stores order details.
  • OrderItems: Stores items within an order.
  • Products: Stores product details.

CREATE TABLE Customers (
    CustomerID INT PRIMARY KEY,
    Name NVARCHAR(100),
    Email NVARCHAR(100),
    CreatedAt DATETIME
);

CREATE TABLE Products (
    ProductID INT PRIMARY KEY,
    ProductName NVARCHAR(100),
    Price DECIMAL(10, 2),
    Stock INT
);

CREATE TABLE Orders (
    OrderID INT PRIMARY KEY,
    CustomerID INT FOREIGN KEY REFERENCES Customers(CustomerID),
    OrderDate DATETIME
);

CREATE TABLE OrderItems (
    OrderItemID INT PRIMARY KEY,
    OrderID INT FOREIGN KEY REFERENCES Orders(OrderID),
    ProductID INT FOREIGN KEY REFERENCES Products(ProductID),
    Quantity INT,
    Price DECIMAL(10, 2)
);
INSERT INTO Customers (CustomerID, Name, Email, CreatedAt)
VALUES 
(1, 'John Doe', 'john.doe@example.com', '2023-01-10'),
(2, 'Jane Smith', 'jane.smith@example.com', '2023-02-15'),
(3, 'Emily Johnson', 'emily.johnson@example.com', '2023-03-22'),
(4, 'Michael Brown', 'michael.brown@example.com', '2023-04-05'),
(5, 'Sarah Davis', 'sarah.davis@example.com', '2023-05-30');


INSERT INTO Products (ProductID, ProductName, Price, Stock)
VALUES 
(1, 'Laptop', 999.99, 50),
(2, 'Smartphone', 499.99, 150),
(3, 'Tablet', 299.99, 75),
(4, 'Headphones', 149.99, 200),
(5, 'Smartwatch', 199.99, 100);

INSERT INTO Orders (OrderID, CustomerID, OrderDate)
VALUES 
(1, 1, '2023-06-15'),
(2, 2, '2023-07-20'),
(3, 3, '2023-08-25'),
(4, 4, '2023-09-10'),
(5, 5, '2023-10-05');

INSERT INTO OrderItems (OrderItemID, OrderID, ProductID, Quantity, Price)
VALUES 
(1, 1, 1, 1, 999.99),
(2, 1, 4, 2, 149.99),
(3, 2, 2, 1, 499.99),
(4, 2, 5, 1, 199.99),
(5, 3, 3, 2, 299.99),
(6, 4, 1, 1, 999.99),
(7, 4, 2, 1, 499.99),
(8, 5, 5, 2, 199.99),
(9, 5, 3, 1, 299.99);

Enhancements to sys.dm_exec_query_statistics_xml 🆕

SQL Server 2022 introduces several key enhancements to sys.dm_exec_query_statistics_xml, including:

  1. Enhanced Plan Information: More detailed execution plan information is now available.
  2. Wait Statistics: Comprehensive wait statistics are included to identify bottlenecks.
  3. Query Store Integration: Better integration with the Query Store for historical analysis.

Demonstrating Enhancements with T-SQL Queries 📊

Let’s dive into some T-SQL queries to see these enhancements in action.

Step 1: Capture a Sample Query Execution

First, we’ll execute a sample query to fetch order details along with customer and product information.

SELECT o.OrderID, o.OrderDate, c.Name AS CustomerName, p.ProductName, oi.Quantity, oi.Price
FROM 
    Orders o
JOIN 
    Customers c ON o.CustomerID = c.CustomerID
JOIN 
    OrderItems oi ON o.OrderID = oi.OrderID
JOIN 
    Products p ON oi.ProductID = p.ProductID
WHERE 
    o.OrderDate BETWEEN '2023-01-01' AND '2023-12-31';

Step 2: Retrieve Query Statistics XML

Next, we’ll use sys.dm_exec_query_statistics_xml to retrieve detailed execution statistics for the above query.

WITH XMLNAMESPACES (DEFAULT 'http://schemas.microsoft.com/sqlserver/2004/07/showplan')
SELECT 
    qst.sql_handle,
    qst.plan_handle,
    qst.execution_count,
    qst.total_worker_time,
    qst.total_elapsed_time,
    qst.total_logical_reads,
    qst.total_physical_reads,
    qst.creation_time,
    qst.last_execution_time,
    q.text AS query_text,
    qpx.query_plan
FROM 
    sys.dm_exec_query_stats AS qst
CROSS APPLY 
    sys.dm_exec_sql_text(qst.sql_handle) AS q
CROSS APPLY 
    sys.dm_exec_query_plan(qst.plan_handle) AS qpx
WHERE 
    q.text LIKE '%SELECT o.OrderID, o.OrderDate, c.Name AS CustomerName, p.ProductName, oi.Quantity, oi.Price%';

Step 3: Analyzing Enhanced Plan Information 🔍

With SQL Server 2022, the execution plan XML now includes more detailed information about the query execution. You can parse the XML to extract specific details.

WITH XMLNAMESPACES (DEFAULT 'http://schemas.microsoft.com/sqlserver/2004/07/showplan')
SELECT 
    query_plan.value('(//RelOp/LogicalOp)[1]', 'NVARCHAR(100)') AS LogicalOperation,
    query_plan.value('(//RelOp/PhysicalOp)[1]', 'NVARCHAR(100)') AS PhysicalOperation,
    query_plan.value('(//RelOp/RunTimeInformation/RunTimeCountersPerThread/ActualRows)[1]', 'INT') AS ActualRows,
    query_plan.value('(//RelOp/RunTimeInformation/RunTimeCountersPerThread/ActualEndOfScans)[1]', 'INT') AS ActualEndOfScans
FROM 
    (SELECT CAST(qpx.query_plan AS XML) AS query_plan
     FROM sys.dm_exec_query_stats qs
     CROSS APPLY sys.dm_exec_query_plan(qs.plan_handle) AS qpx
     WHERE qs.sql_handle = (SELECT sql_handle FROM sys.dm_exec_requests WHERE session_id = @@SPID)) AS x;

Step 4: Monitoring Wait Statistics ⏱️

Wait statistics help identify performance bottlenecks such as CPU, IO, or memory waits. SQL Server 2022 provides enhanced wait statistics in the query execution plans.

WITH XMLNAMESPACES (DEFAULT 'http://schemas.microsoft.com/sqlserver/2004/07/showplan')
SELECT 
    wait_type,
    wait_time_ms AS total_wait_time_ms,
    wait_time_ms - signal_wait_time_ms AS resource_wait_time_ms,
    signal_wait_time_ms
FROM 
    sys.dm_exec_session_wait_stats
WHERE 
    session_id = @@SPID;

Leveraging Query Store Integration 📈

SQL Server 2022’s improved integration with the Query Store allows for historical query performance analysis, helping you understand performance trends and regressions.

SELECT 
    qsp.plan_id,
    qsp.query_id,
    qsqt.query_sql_text AS query_text,
    qsrs.count_executions AS execution_count,
    qsrs.avg_duration,
    qsrs.avg_cpu_time,
    qsrs.avg_logical_io_reads
FROM 
    sys.query_store_runtime_stats qsrs
JOIN 
    sys.query_store_plan qsp ON qsrs.plan_id = qsp.plan_id
JOIN 
    sys.query_store_query qsq ON qsp.query_id = qsq.query_id
JOIN 
    sys.query_store_query_text qsqt ON qsq.query_text_id = qsqt.query_text_id
WHERE 
    qsqt.query_sql_text LIKE '%SELECT o.OrderID, o.OrderDate, c.Name AS CustomerName, p.ProductName, oi.Quantity, oi.Price%';

Conclusion 🎉

The enhancements to sys.dm_exec_query_statistics_xml in SQL Server 2022 provide deeper insights into query performance, making it easier to identify and resolve performance issues. By leveraging these new capabilities, database administrators can ensure their SQL Server instances run more efficiently and effectively.

Feel free to experiment with the queries provided and explore the powerful new features SQL Server 2022 has to offer. Happy querying! 🧑‍💻

Standard

Posted by

Posted on

August 27, 2024

Posted under

SQL Server 2022

Comments

Leave a comment

SQL Server 2022: TIME_ZONE_INFO Function Explained

🕰️SQL Server 2022 introduces the TIME_ZONE_INFO function, enhancing your ability to manage and work with time zone data effectively. This function simplifies handling global applications where time zone differences are crucial for accurate data analysis and reporting.

In this blog, we will explore the TIME_ZONE_INFO function, provide a detailed business use case, and demonstrate its usage with T-SQL queries using the JBDB database.🕰️

Business Use Case: Global E-commerce Platform 🌐

Consider Global Shop, an international e-commerce company operating across multiple time zones. To provide a consistent user experience and synchronize order processing times, Global Shop needs to handle time zone conversions accurately. The TIME_ZONE_INFO function in SQL Server 2022 will be instrumental in managing these time zone differences.

Setting Up the JBDB Database

First, let’s set up the JBDB database and create a sample table Orders to illustrate the use of the TIME_ZONE_INFO function.

-- Create JBDB database
CREATE DATABASE JBDB;
GO

-- Use the JBDB database
USE JBDB;
GO

-- Create Orders table
CREATE TABLE Orders (
    OrderID INT PRIMARY KEY,
    CustomerID INT,
    OrderDateTime DATETIMEOFFSET,
    TimeZone VARCHAR(50),
    Amount DECIMAL(10, 2)
);
GO

-- Insert sample data into Orders
INSERT INTO Orders (OrderID, CustomerID, OrderDateTime, TimeZone, Amount)
VALUES
    (1, 101, '2024-07-01 14:00:00 -07:00', 'Pacific Standard Time', 100.00),
    (2, 102, '2024-07-01 17:00:00 -04:00', 'Eastern Standard Time', 200.00),
    (3, 103, '2024-07-01 19:00:00 +01:00', 'GMT Standard Time', 150.00),
    (4, 104, '2024-07-01 22:00:00 +09:00', 'Tokyo Standard Time', 250.00);
GO

Understanding TIME_ZONE_INFO Function 🧩

The TIME_ZONE_INFO function provides information about time zones, such as their offsets from Coordinated Universal Time (UTC) and daylight saving time rules. This function helps in converting between different time zones and understanding how time zone changes affect your data.

Syntax

TIME_ZONE_INFO(time_zone_name)
  • time_zone_name: The name of the time zone for which information is required, such as 'Pacific Standard Time'.

Example Queries

  1. Get Time Zone Offset for a Specific Time ZoneRetrieve the current offset from UTC for a specific time zone using sys.time_zone_info:
SELECT tz.name AS TimeZoneName 
       ,tz.current_utc_offset AS UTCOffset
FROM sys.time_zone_info tz
WHERE tz.name = 'Pacific Standard Time';

Convert Order DateTime to UTC

Convert the OrderDateTime from different time zones to UTC for consistent reporting:

SELECT OrderID, CustomerID, OrderDateTime AT TIME ZONE 'Pacific Standard Time' AS LocalTime,
       OrderDateTime AT TIME ZONE 'UTC' AS UTCTime, Amount
FROM Orders;

Find Orders Placed in a Specific Time Range (in Local Time)

Find orders placed between specific times in the ‘Pacific Standard Time’ time zone:

SELECT OrderID, CustomerID, OrderDateTime, TimeZone, Amount
FROM Orders
WHERE OrderDateTime AT TIME ZONE 'Pacific Standard Time' BETWEEN '2024-07-01 00:00:00' AND '2024-07-01 23:59:59';

Find Orders Based on UTC Time Range

Find orders placed within a UTC time range:

SELECT OrderID, CustomerID, OrderDateTime, TimeZone, Amount
FROM Orders
WHERE OrderDateTime AT TIME ZONE 'UTC' BETWEEN '2024-07-01 00:00:00' AND '2024-07-01 23:59:59';

Analyze Orders with Different Time Zones

Group orders by their time zones and calculate the total amount for each time zone:

SELECT TimeZone, COUNT(*) AS NumberOfOrders, SUM(Amount) AS TotalAmount
FROM Orders
GROUP BY TimeZone;

Find Orders with NULL Values in Time Zone Column

Identify orders where the time zone information is missing:

SELECT OrderID, CustomerID, OrderDateTime, TimeZone, Amount
FROM Orders
WHERE TimeZone IS NULL;

Find Orders Where Local Time is in a Specific Range

Find orders where the local time in the ‘Eastern Standard Time’ zone is within a specific range:

SELECT OrderID, CustomerID, OrderDateTime AT TIME ZONE 'Eastern Standard Time' AS LocalTime, Amount
FROM Orders
WHERE OrderDateTime AT TIME ZONE 'Eastern Standard Time' BETWEEN '2024-07-01 10:00:00' AND '2024-07-01 15:00:00';

List Orders by Time Zone and Date

List orders sorted by time zone and the date they were placed:

SELECT OrderID, CustomerID, OrderDateTime, TimeZone, Amount
FROM Orders
ORDER BY TimeZone, OrderDateTime;

Convert and Compare Orders Between Two Time Zones

Compare orders placed in two different time zones:

SELECT OrderID, CustomerID, 
       OrderDateTime AT TIME ZONE 'Pacific Standard Time' AS PSTTime,
       OrderDateTime AT TIME ZONE 'Eastern Standard Time' AS ESTTime,
       Amount
FROM Orders;

Find Orders Where Time Zone is Not Standard

Identify orders where the time zone is not a standard time zone from the list:

SELECT OrderID, CustomerID, OrderDateTime, TimeZone, Amount
FROM Orders
WHERE TimeZone NOT IN (SELECT name FROM sys.time_zone_info);

Detailed Business Use Case 🌍

Scenario: Global Shop needs to analyze sales performance by region while considering time zone differences. The company aims to:

  1. Aggregate Sales Data: Calculate total sales and the number of orders for each time zone.
  2. Convert Local Time to UTC: Ensure all reports reflect a consistent time standard (UTC).
  3. Track Orders: Identify orders placed within specific time ranges in different time zones.

Workflow:

  1. Aggregation: Use the TIME_ZONE_INFO function to group orders and analyze sales data by time zone, aiding in regional performance assessments.
  2. Time Conversion: Convert local order times to UTC using the AT TIME ZONE function to ensure consistent reporting across different time zones.
  3. Reporting: Generate reports based on both local and UTC times, providing a clear and accurate picture of order activity across time zones.

Conclusion 🏁

The TIME_ZONE_INFO function in SQL Server 2022 is a valuable tool for managing and analyzing time zone data. It simplifies time zone conversions and enhances the accuracy of time-based queries, crucial for handling global applications like Global Shop.

By utilizing this function, you can ensure consistent and accurate time data management, improving the reliability of your reports and analyses. 🌟

Feel free to use the provided queries and examples as a starting point for your time zone-related tasks in SQL Server 2022. If you have any questions or need further assistance, drop a comment below! 👇

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.