Loops, Transactions, and Transaction Log Writes In SQL Server
Thanks for watching!
Going Further
If this is the kind of SQL Server stuff you love learning about, you’ll love my training. I’m offering a 75% discount to my blog readers if you click from here. I’m also available for consulting if you just don’t have time for that, and need to solve database performance problems quickly. You can also get a quick, low cost health check with no phone time required.
Related Posts
- A Little About Parameter Sensitive Plan Optimizations In SQL Server 2022
- IF Branching In SQL Server Stored Procedures: Dynamic SQL!
- IF Branching In SQL Server Stored Procedures: Fixing Parameters, Recompiling, And A Good Enough Plan
- IF Branching In SQL Server Stored Procedures: Patterns And Problems
This was very eye-opening. The decrease in log writes makes sense, but the reduction in run time was more than I expected. Of course, the trade-off with not committing transactions so often is the increased chance of blocking, so, as with most things, it’s a balancing act.
Well, okay, but which modification has a better chance of causing blocking? Seven seconds, 2 seconds, or a few milliseconds?