See how you can use Extended Events to find your worst performing checkpoints.
It's a few days later than many of us were expecting, but Cumulative Update #2 for SQL Server 2019 (15.0.4013.40) is overflowing with 134 fixes and enhancements.
Security updates were released today to patch a remote code execution vulnerability in Reporting Services, but I would install the patch even if you're not running SSRS.
This month, Jess Pomfret hosts T-SQL Tuesday, and asks us to talk about our own personal life hacks that make our day easier.
SQL Server 2017 Cumulative Update #19 is available. The build # is 14.0.3281.6 and there are 38 fixes.
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.
Find out about the replacement I wrote for the undocumented, unsupported, and ill-advised system procedure, sp_MSforeachdb.
In this tip, I show how soft deletes and a filtered index can help minimize the cost of ghost records in an Availability Group.
I add some details about phase 2 of my home office changes.
I detail my home office setup, much of the gear in it, and show the progress of a minor renovation – a new standing desk and improved backlighting.
For this month's T-SQL Tuesday, I talk a little bit about how I make my imposter syndrome feel less like imposter syndrome.
SQL Server 2019 Cumulative Update #1 is now available, with 83 fixes and improvements. Build # is 15.0.4003.23.
I continue my series on investigating compression for a 1TB table, honing in on clustered columnstore and partitioning.
In this tip, I show how and why a columnstore index can provide benefits to COUNT(*) queries.
With another new year comes the recognition of a standout contributor to the SQL Server community. Read on to see 2019's honoree.
I start a series looking at using clustered columnstore indexes and page compression to address storage footprint for a 1TB table.
I show how I tried to chase down a very unexpected issue with SQL Server metadata. Spoiler: it didn't end the way I thought it would.
For this month's T-SQL Tuesday, I talk about an opportunity earlier this year to significantly change my career trajectory.
Discover a simple way to keep your filtered indexes effective – even under forced parameterization.
Conventional wisdom has suggested that deletes should be batched, but in some cases this can actually take a lot longer.