A brand new video covering the performance impact of delayed Durability vs Optimistic Concurrency. Which is better? While both have different behavior and purpose; when it comes down to the basic task at hand both essentially improve write (and in the latter’s case read) performance, so the question was can they be used together, do their performance improvements add up? If enabling delayed durability does it make sense to do it on tempdb or the user database? Some interesting results come out of this video and some weird behavior when MAXDOP =1 but more on that in the next video.
Here’s the link and please feel free to let me know your thoughts.
This post was written by Jayanth Kurup. A Microsoft SQL Server Consultant and Trainer based out of Bangalore, India. Jayanth has been working on MS SQL Server for over 15 years. He is a performance tuning and Business Intelligence expert. Having worked with companies like Microsoft, DELL, Wells Fargo, Thomson Reuters and many other fortune 100 companies. Some other technologies Jayanth works on include Microsoft Azure, PowerBI, Python and AWS. When he isn’t consulting or training, Jayanth like to travel, paint and read. He is also very active in social causes and the founder of Enabled Business Solutions. Visit his company by clicking the link in the menu or email him directly.
