Had something like this in a mock. Shrinking the transaction log won't help with PAGELATCH_UP waits, since those are usually from contention on in-memory data pages, not the log file size. Pretty sure B is right here-correct me if I'm missing something.
Q: 8
You have an instance of SQL Server on Azure Virtual Machine named SQL1.
You need to monitor SQL1 and query the metrics by using Kusto query language. The solution must
minimize administrative effort.
Where should you store the metrics?
Options
Discussion
Option A is right here. Log Analytics workspace is built for Kusto queries and makes monitoring SQL on VMs straightforward. Event Hubs (B) isn’t really for metric analysis, more for streaming events. Anyone disagree?
A tbh . Shrinking the log just frees up disk space, it doesn't address PAGELATCH_UP wait types. Those usually point to tempdb or hot page contention, not something you fix by messing with the log file. Trap answer here! Someone else see it differently?
Be respectful. No spam.
Question 8 of 35