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,791 reads
Learn about transaction ID wraparound in PostgreSQL, which caused a problem for the author.
2026-02-23 (first published: 2026-02-13)
1,791 reads
Learn how backup and restore work in Azure SQL Hyperscale in this next level in the stairway series.
2025-12-17
789 reads
In this level, we learn about the database file size growth in Hyperscale.
2025-12-03
85 reads
Learn about filtered indexes in SQL Server, how they work, and how they can help improve performance.
2025-11-24
4,078 reads
Learn about unlogged tables and how they work in PostgreSQL.
2025-11-21
4,770 reads
Learn about a MySQL feature that could be useful in some scenarios for SQL Server.
2025-11-10
4,257 reads
Learn about how the Log Service helps manage transactions in the Hyperscale Tier.
2025-10-29
1,070 reads
Learn about implicit transaction and why you might not want to enable this setting.
2025-10-24
6,481 reads
In this level of the Stairway to Azure SQL Hyperscale we learn about the read-only layer that speeds up queries.
2025-10-08
432 reads
Learn how a setting an improve high concurrency inserts with the OPTIMIZE_FOR_SEQUENTIAL_KEY option.
2025-10-01
6,072 reads
By Vinay Thakur
Continuing from Day 3 where we covered LLM models open/closed and their parameters, Today...
By Steve Jones
One of the nice things about Flyway Desktop is that it helps you manage...
By HeyMo0sh
Microsoft Fabric (not to be confused with the more general term “fabric” in DevOps)...
I'm fairly certain I know the answer to this from digging into it yesterday,...
Hi Team, I am trying to refresh the Azure Synapse Dedicated pool from production...
hi everyone I am not sure how to write the query that will produce...
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