About a month ago we upgraded an application to a later version and as part of the upgrade we moved from Windows 2012 to 2019 and SQL 2014 to 2017. We are now seeing regular PAGELATCH_SH and PAGELATCH_EX waits on a couple of objects in TEMPDB, particularly between about 9am and 11am.
According to DBCC PAGE they are on sysallocunits and syssingleobjrefs. I am assuming this is an application issue so have raised a call with the vendor but is there anything I can do from an administration point of view to try and reduce the impact? I believe that adding more TEMPDB files in this situation will make no difference?
I'd focus on the queries to see what's causing the pain. Document it for the vendor. Also, maybe a judicious index or a plan guide could fix the issue. Capture the query metrics, blocking and waits. Get the execution plan.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply