Downtime Caused by the Postgres Transaction ID Wraparound Problem
Learn about transaction ID wraparound in PostgreSQL, which caused a problem for the author.
2026-02-23 (first published: 2026-02-13)
1,813 reads
Chandan Shukla
Filtered Indexes: The Developer’s Secret Weapon in SQL Server
Learn about filtered indexes in SQL Server, how they work, and how they can help improve performance.
2025-11-24
4,138 reads
UNLOGGED Tables in PostgreSQL: When Speed Matters More Than Durability
Learn about unlogged tables and how they work in PostgreSQL.
2025-11-21
4,858 reads
MySQL’s BLACKHOLE Storage Engine: The Odd Feature I Wish SQL Server Shipped With
Learn about a MySQL feature that could be useful in some scenarios for SQL Server.
2025-11-10
4,261 reads
How Implicit Transactions Hurt SQL Server Performance Without You Knowing
Learn about implicit transaction and why you might not want to enable this setting.
2025-10-24
6,514 reads
Unlocking High-Concurrency Inserts in SQL Server with OPTIMIZE_FOR_SEQUENTIAL_KEY
Learn how a setting an improve high concurrency inserts with the OPTIMIZE_FOR_SEQUENTIAL_KEY option.
2025-10-01
6,169 reads
When Page Prefetching Takes a Back Seat – Exploring Trace Flag 652 in SQL Server
Learn how a trace flag affects SQL Server reading from disk and where this might be a useful thing for you to enable.
2025-09-24
2,472 reads
Revisiting SQL Server Window Functions- A Practical Walkthrough
A look at window functions in SQL and how they can be used to query data without the restrictions of a GROUP BY.
2025-09-12
6,901 reads
Advanced SQL Server Page Forensics: Detecting Page Splits and Allocations with DBCC PAGE
Page splits are an often-overlooked performance killer in SQL Server. In this article, we take a forensic look at how serial inserts differ from mid-table inserts, revealing why inserting rows out of order causes hidden page splits, increased IO, and fragmentation. Using a wide-column table, we demonstrate both scenarios and decode their impact with page-level analysis.
2025-09-02 (first published: 2025-08-05)
2,553 reads
Deprecated but Forgotten: Why SQL Server’s Text, NText, and Image Data Types Still Haunt Your Systems
TEXT, NTEXT, and IMAGE columns have been deprecated for nearly two decades, yet they still silently haunt many SQL Server environments. This article explains their hidden limitations with practical demos and shows why migrating to VARCHAR(MAX), NVARCHAR(MAX), and VARBINARY(MAX) is critical for modern performance, maintainability, and future upgrades.
2025-09-02 (first published: 2025-08-06)
2,614 reads
Blogs
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Shifting Mindsets: Why FinOps is Essential for Cloud Efficiency
By HeyMo0sh
As a DevOps practitioner, I’ve always focused on performance, scalability, and automation. But as...
Forums
how to write this query?
Hi everyone I asked this earlier but the desired outcome is a bit different...
Windows logins for users migrated from DomainA to DomainB
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Multiple Deployment Processes
Comments posted to this topic are about the item Multiple Deployment Processes
Question of the Day
Upgrading Admin Queries
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers