SQL Server 2019 Cumulative Update #5 is available, with 86 enhancements. The build number is 15.0.4043.16.
Category: SQL Server
See two ways you can make the relevant data in the system_health session last longer and not get drowned out by noise.
SQL Server 2016 SP2 Cumulative Update #13 is available, with 29 enhancements. The build number is 13.0.5820.21.
Access the system_health file target without tedious string parsing gymnastics.
This series shows how I determine the amount of data distributed across indexes, files, filegroups, and partitions.
Dig into an intermittent stack dump involving an aggregate query against a heap with a LOB column.
Discover some undocumented or unsupported behavior you might not even realize you're relying on.
An index of over a decade's worth of posts and videos involving bad habits and best practices in SQL Server.
See a quick T-SQL script for determining how often Cinco de Mayo falls on Taco Tuesday.
I continue a series where I dig into how data is distributed across indexes, files, and filegroups.
I talk about a recent change where I started turning on indirect checkpoints across all user databases.
I finish up my series on replacing the default trace with views to simplify consumption and a caveat about reports in SSMS.
See the stored procedure I wrote to help me put all file, filegroup, and index information in one place.
I continue my series on replacing the default trace with a more efficient and more complete Extended Events session.
See a quick example where plan shape can cause errors that really shouldn't happen.
In this tip, see ways you can change how a function is called without having to modify all calling code at the same time.
Need to get data, log, or bak files into your container's file system? See how, with
I start a series explaining how I evaluated the default trace and decided to replace it with a slimmer Extended Events session across all of production.
See how you can use Extended Events to find your worst performing checkpoints.
In this tip, I talk about a concerning behavior in the dynamic management function, sys.dm_db_database_page_allocations.
I continue my series on large table compression with results from row and page compression as well as a process involving scheduler manipulation.