[Video] Office Hours: Fireside Chat Edition
It’s the perfect time of year in Las Vegas when we can chill outside by the fire, enjoy a glass of wine, and go through your top-voted questions from https://pollgab.com/room/brento.
Here’s what we covered:
- 00:00 Start
- 00:54 iliyan Rashev: Hello Brent, I am on SQL Server 2019 RTM Please recommend a patching path: 1. Apply CU32+latest Sec.update 2. Apply only latest Sec.update In other words using the 2nd approach will be faster,but do I get all the previous fixes from CU32 that contain all fixes from previous CUs?
- 02:51 DBArchitectChick: Brent, I am trying to solve the struggle in my head. I admit I love stored procedures. I even wrote a robust unit testing suite for them. Unfortunately, my fellow application developers call them “code smell”. Do I need to give up on pressing for SPs? I might need therapy
- 06:05 Elwood Blues: What are the top issues you see when running SQL Server on VM’s with multiple NUMA nodes / high core count?
- 08:53 Adrian: Hi, I saw code, not mine, that purges old data reading WITH READPAST and deleting from tables using joins and ROWLOCK, READPAST for the table where it deletes and READPAST for the tables in the join. I want to know if it is safe, a good idea, are better options? No RCSI
- 10:23 stittdba: In the past, there used to be a good rule of thumb to wait for SP1 before migrating to a new version of SQL Server. With SPs now a thing of the past, what general guidance would you offer for a time to migrate to a new version?
- 10:25 stittdba: In the past, there used to be a good rule of thumb to wait for SP1 before migrating to a new version of SQL Server. With SPs now a thing of the past, what general guidance would you offer for a time to migrate to a new version?
- 11:57 BrentFanBoy: Hi Brent, I have a server that is under heavy load and need to catch an SP that runs very fast, unfortunately it does updates and deletes so I can’t run it myself. What is the best way of catching query plans and runtime stats for that SP?
- 14:49 Harold Bright: Hi Brent, Is there a way in MSSQL Server where i can call the procedures in Async Mode? i.e. Calling parent proc which has couple of procs to be execute. At present it goes subsequently, but is there a way i can get it started together?
5 Comments. Leave new
Hi Brent, There are two things I do with stored procedures that I need execution plans for and first is to check the Procedure Cache to see if that proc is cached. If so that gives you the execution plans for each CRUD statement. The next thing I would suggest is to take the INSERT and UPDATE statements and convert them into SELECT statements and get execution plans for those statements.
If this is being done from a C# app that is using ADO SqlCommand the best way of doing this is replacing SqlCommand in the Global Usings and then run that SqlCommand for that stored proc in Development and capture the stored procedure’s execution plan by getting them during my testing process. I report in the code filename and line number of where that proc is getting called in the C# but also checks to turn on/off certain checks or turning itself off if my code determines that the SQL is running correctly. Because this is a Global Using replacement and that code isn’t in the production release it only shows up the non-Production builds.
Hi Brent, I was on your free (cheers, dude) Foundation and Mastering weeks, recently, and I was sure you’d persuaded me to dive straight in with SQL 2025 rather than hanging a version behind. The reasoning you gave at the time was that compat levels are now pretty faithful to the OG version, so there’s no need to wait. With this fireside chat, you’ve unsettled me a little – so what’s the craic, on that score? Takk fyrir!
Great question! For personalized advice on your own situation, feel free to join one of my paid classes, or click Consulting at the top of the screen. Hope that’s fair. Cheers!
Another way to run stored procs asynchronously is using service broker. Create a message type, contract and queue for each stored proc (with your stored proc as the queue’s activation procedure). In your calling stored proc, submit 4 conversations (messages) to the broker. Takes some setting up (ChatGPT can probably help) but it works really well for us.
That’s true too!