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,788 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,069 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,767 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,257 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,480 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,067 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,465 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,870 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,541 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,554 reads
Blogs
What DevOps Look Like in Microsoft Fabric
By HeyMo0sh
Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...
T-SQL Tuesday #192: What career risks have you taken?
By James Serra
I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...
AI: Blog a Day – Day 3: LLM Models – Open Source vs Closed Source
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
Forums
Best Digital Marketing Strategies
Having trouble attracting leads or visibility online? We develop the best digital marketing strategies...
Best Social Media Marketing Company
Posting regularly but not getting engagement or sales? As one of the best social...
Azure Synapse database refresh
Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...
Question of the Day
Fun with JSON I
I have some data in a table:
CREATE TABLE #test_data
(
id INT PRIMARY KEY,
name VARCHAR(100),
birth_date DATE
);
-- Step 2: Insert rows
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT *
FROM OPENJSON(
(
SELECT t.* FROM #test_data AS t FOR JSON PATH
)
) t; See possible answers