ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #microsoftsqlserver
Query Store turns SQL Server plan regressions from guesswork into evidence. Learn how to enable it, capture query history, force a known-good plan, and avoid the storage and replica traps.
A large fact table makes aggregations painful. Columnstore cuts I/O with columnar compression and batch mode, but CCI and NCCI have different transactional and maintenance implications.
Learn how SQL Server temporal tables automatically keep a full history of row changes, letting you query past states with simple FOR SYSTEM_TIME clauses—no triggers required.
When you need to audit every row change without writing triggers, system‑versioned temporal tables let you store full history automatically. Learn how to enable them, query past data, and what trade‑offs to consider for production workloads.
Deploy clustered or nonclustered columnstore indexes to dramatically speed up large‑table analytics in SQL Server. This guide walks through prerequisites, creation steps, performance checks, and fallback strategies, ensuring you can confidently use columnstore for high‑throughput reporting.
Temporal tables in SQL Server let you query past data without custom audit logic. Learn how to create, index, and manage history tables, and see a concrete example of point‑in‑time queries and storage trade‑offs.
Enabling READ COMMITTED SNAPSHOT can stop readers and writers from blocking each other, but it shifts pressure to tempdb and does not remove writer-writer conflicts.
Learn the smallest viable Always On AG that guarantees zero data loss, its trust boundaries, key operational checks, and when to revisit the design.
A query that is fast for one parameter and slow for another often suffers from parameter sniffing. Learn how to confirm it with DMVs and execution plans, then stabilize performance.