ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #microsoftsqlserver
When a SQL Server query suddenly slows down without code changes, Query Store captures execution plans over time so you can compare them and force a known-good plan back into service.
Learn how to use SQL Server Query Store to capture execution history, compare plans across deployments, and force a stable plan when the optimizer picks a bad one.
Enable SQL Server Query Store with a production-ready configuration, learn to spot plan regressions using catalog views, force plans safely, and avoid the common mistakes that silently disable capture or cause forced-plan regressions.
Guide to picking SQL Server In‑Memory OLTP vs. disk‑based tables for high‑throughput OLTP, with a comparison table, trade‑offs, and a concrete implementation example.
Columnstore indexes can turn a 14-minute SQL Server aggregation into seconds — or make your OLTP table miserable. Here's how the storage model works, a worked CCI example, and the checks that tell you which side you're on.
Facing huge tables that take hours to rebuild indexes? Table partitioning in SQL Server lets you rebuild or backup individual segments, cutting maintenance time dramatically. This guide walks through the concept, a concrete example, and how to verify the benefits.
A decision guide for SQL Server recovery models: when FULL is mandatory, when SIMPLE is honest, how to scope BULK_LOGGED, and how to validate point-in-time restore before you need it.
Learn how to spot PAGELATCH_UP waits on TempDB pages, check configuration, apply fixes, and verify improvement.
Learn how to implement Clustered Columnstore Indexes in SQL Server to enable HTAP workloads, reduce I/O, and accelerate analytical queries on live transactional data.