Cumulative Updates for SQL Server 2019, SQL Server 2017, and SQL Server 2016 SP2 have been pushed back a month 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!
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
SQL Server 2019 Cumulative Update #3 is available, with 56 enhancements. The build number is 15.0.4023.6.
With the increasing number of office closures, I share some tips about working from home.
In this tip, I show how to measure the positive effects of delayed durability, in cases where a small amount of data loss is acceptable.
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.