See two ways you can make the relevant data in the system_health session last longer and not get drowned out by noise.
For this month's T-SQL Tuesday, let's talk about something you're more likely to hear from a carpenter: Measure twice, cut once.
See how to work around some of the blockers for replacing legacy UDFs with STRING_SPLIT.
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.
Cumulative Updates for SQL Server 2019, SQL Server 2017, and SQL Server 2016 SP2 have been pushed back a month or more due to our current health crisis.
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.
SQL Server 2017 Cumulative Update #20 is available, with 40 enhancements. The build number is 14.0.3294.2.
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.
SQL Server 2019 Cumulative Update #4 is available, with 50 enhancements. The build number is 15.0.4033.1.
See how blogging can benefit both the author and the reader in this short opinion piece.
Phase 3 of my home office – doors! – couldn't have happened at a better time.
I want to push for improvements to STRING_SPLIT in the next version of SQL Server. See how you can help!