sqlblogcasts.com Editors publishes concise technical notes about SQL Server for database administrators and developers. The notes explain why a query, transaction log, or SQL Agent job behaves in a particular way and give reproducible steps to fix or verify the problem. The focus is SQL Server 2016, 2017, 2019, and 2022.
The typical reader has a specific issue: a scalar UDF that forces a serial plan, a transaction log that keeps growing, or a job that fails only under load. We explain the mechanism before the fix, so you can decide whether the change is safe in your environment.
What we publish
Each note states the problem it solves, lists the requirements, shows the T-SQL or configuration steps, and gives the expected output. We state the SQL Server version and compatibility level where it matters, for example SQL Server 2019 (compatibility level 150).
Typical topics include:
- Execution plans and cardinality estimates
- Transaction log growth and recovery
- SQL Agent job failures and waits
- Index fragmentation and maintenance
- Extended Events and DMV queries
Each note also lists common errors and how to verify that the fix worked, with the expected output of DBCC or a DMV query. You will not find generic round-ups or claims like “best SQL Server blog”. Each note is built around a reproducible scenario. Where a change could affect data, we first recommend testing on a restored copy and taking a backup.
How we research and write
We work from primary sources: Microsoft Learn documentation, DMV output, Extended Events, and execution plans. When a behaviour depends on the version or cumulative update, we say so, for example “tested on SQL Server 2019 CU18” or “behaviour differs before SQL Server 2016 SP1”. We link to Microsoft Learn pages where they add context. We record the compatibility level and cumulative update because these details change query behaviour.
When we use information from a blog or forum, we check it against Microsoft documentation or a test instance before relying on it. We do not sign notes with individual names; the editorial voice is the site’s editors. We do not publish performance figures without a reproducible query.
Corrections
If you find an error, please tell us. We review reported errors and add a correction note to the article with the date and what changed. Comments are disabled, so the contact channels are the way to reach us.
Independence
sqlblogcasts.com Editors is an independent project, not affiliated with any similarly named organisations or with anyone who used the domain before, and it does not speak on behalf of the original SQLBlogCasts community or its former bloggers.
Contact and legal pages
To contact the editors, use the site’s contact channels. For details on how this site handles data, read the privacy policy. For the conditions of use, read the terms of use.
Last updated: 11 November 2026.