[Video] Office Hours: Long Answers Edition

This week’s top-voted questions from https://pollgab.com/room/brento finds us opening ChatGPT multiple times! It’s fun to show how I use it, and what it thinks of me.

Prefer listening to this via podcast? Good news! You can now subscribe to Office Hours on Spotify, Apple Podcasts, Podcast Index, Podcast Addict, Podchaser, and anywhere else fine podcasts are sold.

Here’s what we covered:

• 00:00 Start
• 06:36 DBAInAction: Hi Brent! We’re seeing HADR_SYNC_COMMIT waits causing brief app outages on random days, but consistently between 2-4 AM PT. No app changes, and we only run backups (no user workloads) on the sync secondary. How can we pinpoint the root cause and prevent this? Thank you!
• 12:38 Thomas Franz: Doesn’t it make more sense to index valid_to instead of valid_from (table with multiple rows for an @id)? The latest valid_from is usually unknown, but I know that the valid_to must be greater than @date to find the correct entry for a given date. But I see always indexes on valid_from.
• 16:59 rookieDba: Our DB is in RC isolation level. We own both code and db. I want to enable RCSI, and will analyze the code for concurrency problems from RCSI. It is my understanding that possible NEW concurrency bugs will be in multi -statement transactions – is this correct?
• 23:43 AndrewG: Hi Brent, do you have a blog post or video that goes over the advantages and disadvantages of different databases. For example MSSQL vs MYSQL VS Postgres VS Oracle etc. I know through your training classes it sometimes gets sprinkled in. Thank you!
• 25:56 MyTeaGotCold: I remember that the release of SQL Server 2022 was quite rough and that people were right to avoid migrating for quite a while. Are you seeing any of the same signs with SQL Server 2025?
• 27:52 Elwood Blues: TempDb frequently gets close to running out of space. Before we move it to a larger more expensive azure drive, is there a good way to see which queries are using large amounts of TempDb?
• 29:24 TeaEarlGrayHot: After creating a filtered index recently, I found the query did not use the filtered index but used the existing indexes more efficiently. In this case would it be better to add a filtered statistic or leave the filtered index?