I drove the Graffiti Gulf out to The Last Spike (video) outside of Las Vegas and took your top-voted questions from https://pollgab.com/room/brento.

Here’s what we covered:

• 00:00 Start
• 01:45 Jan de Graaf: Our database landscape seems CPU-bound. We sometimes hit 100% CPU with organic load. We’re considering new hardware. Do you think memory speed plays a significant role? As in 4800MT/s vs. 6400MT/s.
• 03:37 Worried: My SQL Server database had CRC errors and CHECKDB corruption, with no good backups. Copy Database Wizard failed, so we finally scripted out the schema + data and imported it into a new database. Is there a better or safer way to recover in this situation?
• 06:34 Elwood Blues: What is your opinion of SQL database in Microsoft Fabric?
• 07:41 Elwood Blues: What’s your take on cycling the error log in SQL Server? Should we be doing this nightly via a job?
• 08:03 TokTik: Could you please share a bit more about the “NUMA” Poison Wait? It appears in the results of sp_Blitz, and I’m curious whether I should reach out to the VM Team regarding SQL Server’s setup.
• 09:05 MyTeaGotCold: What is the biggest database that you have seen on Standard Edition that could manage weekly CHECKDB?
• 11:23 RoJo: SQL is written in islands in the company: reports, c# code, devs.. Where is the proper placement of the poor ol’ DBA who has to find their bad queries? In the front (traffic cop) or in the end (safety net-debugger of bad performance in Prod). This seems very tricky either way.
• 14:52 Josef: A table in SQL Server suddenly lost data and columns. What’s the simplest way to see the history of what happened to that table? Can the transaction log show it, and are there any other reliable ways to check what changed?
• 18:17 I_like_SQL_Server: Hola Muchacho Brent! What is your favorite new feature of SQL Server 2025 and why? I’m psyched about the columnstore improvements and the persisted statistics for secondaries. Thanks for your continuous contribution to the community!