DP-300 Certification Practice Question #130

Question

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You have SQL Server 2019 on an Azure virtual machine.
You are troubleshooting performance issues for a query in a SQL Server instance.
To gather more information, you query sys.dm_exec_requests and discover that the wait type is PAGELATCH_UP and the wait_resource is 2:3:905856.
You need to improve system performance.
Solution: You shrink the transaction log file.
Does this meet the goal?

Accepted Answer

The wait resource `2:3:905856` points to Database ID 2, which is `tempdb` (1 is master, 2 is tempdb, 3 is model, 4 is msdb). A wait type of `PAGELATCH_UP` in tempdb indicates page allocation or update latch contention (such as PFS, GAM, or SGAM page contention) within tempdb's data files. Shrinking the transaction log file does not resolve tempdb data page allocation contention; instead, solutions typically involve increasing the number of tempdb data files, enabling trace flag 1118 (or using default SQL Server 2016+ behaviors), or optimizing tempdb usage.

More DP-300 practice questions