Troubleshooting Slow Queries That Already Have an Index
This article looks at some common query patterns that cause performance issues and provides some guidance on how to fix them.
2026-11-02
2,501 reads
SQL Server
Finding Gaps in Sequential Data Using SQL Server
Many systems expect a sequential range of numbers for invoices, ticket numbers, and more. Learn how you can identify where you have gaps in your sequences.
2026-09-21
3,888 reads
OUTER APPLY Fundamentals: Part 2
In Part 2 of this series we learn how OUTER APPLY can be used in your queries to return data, even when there are no matches between tables.
2026-08-12
3,487 reads
Managing Changesets Over Time: Stairway to Reliable Database Deployments Level 6
As database changesets accumulate over time, they gradually become more than deployment artifacts. This level explores how a well-organized changeset library evolves into a replayable representation of the database’s structural history, supporting not only reliable deployments but also reconstruction, auditing, and long-term maintainability. Through practical examples and a real-world case study, it shows why maintaining coherent Create and Rollback scripts continues to provide value long after a successful production deployment.
2026-08-05
715 reads
CROSS APPLY Fundamentals: Part 1
Learn the basics of the CROSS APPLY operator with a few examples in this short piece.
2026-07-27
6,574 reads
TRY_PARSE vs TRY_CONVERT in SQL Server: From Basics to Practical Usage
This article shows how the TRY_PARSE() and TRY_CONVERT() functions can be used to handle data quality issues and ensure that your software continues to function without throwing errors.
2026-07-13
3,855 reads
SQL Server Enum Implementation: A Single-Row View Strategy for Avoiding Magic Values
Learn about an alternative strategy for avoiding hardcoded literal values in SQL Server queries by using single-row views designed to mimic enum behavior.
2026-06-26
3,580 reads
Concurrency and Baseline Control: Stairway to Reliable Database Deployments Level 5
As database development scales across multiple contributors, concurrency becomes an inherent aspect of the process. Changes that are individually correct may still conflict when developed against a shifting baseline. This level introduces a disciplined approach to managing parallel changesets by controlling their scope, identifying overlap, and resolving conflicts through realignment. By ensuring that only one changeset retains its original baseline while others are adapted accordingly, deployments remain predictable and consistent. Once released, changesets are treated as immutable, and further evolution proceeds through new, forward-only changes.
2026-06-24
1,245 reads
Preparing for Production Deployment: Stairway to Reliable Database Deployments Level 4
This level examines how a rehearsed changeset is transformed into production-ready deployment artifacts. By consolidating scripts into controlled execution units and validating the resulting artifacts, the approach ensures that production deployment remains predictable and aligned with what was proven during rehearsal.
2026-06-10
1,213 reads
Understanding SQL Server PARTITION BY with Examples
Introduction When developers first learn SQL aggregation, they usually start with the GROUP BY clause. It works well for summary reports because it combines multiple rows into a single result for each group. For example, you can calculate total sales per region or average salary per department. The limitation of GROUP BY appears when you […]
2026-06-05
4,689 reads
Blogs
The #MS_DatabaseConnector## Role: #SQLNewBlogger
By Steve Jones
I had seen these roles in various instances, but never dug into the new...
Asking for Help Isn’t a Weakness
By Brian Kelley
During COVID, I attended training on software/enterprise architecture given by Mark Richards. One of...
The Proof of the Backup Is in the Pudding
For me, the objective is straightforward: have a backup strategy that is reliable, understandable,...
Forums
Pay for Performance
Comments posted to this topic are about the item Pay for Performance, which is...
Access + ODBC Driver 18 + SQL Server 2025: ~150–250 ms per request
Has anyone encountered recurring request latency when using Microsoft Access with SQL Server 2025...
The ##MS_DatabaseConnector## User
Comments posted to this topic are about the item The ##MS_DatabaseConnector## User
Question of the Day
The ##MS_DatabaseConnector## User
On SQL Server 2025, I run this code as a sysadmin:
CREATE LOGIN Demo WITH PASSWORD = 'Demo1234567' GO ALTER SERVER ROLE ##MS_DatabaseConnector## ADD MEMBER Demo GOI then login as Demo and run this:
USE sandbox go SELECT CURRENT_USERWhat is returned? See possible answers