SG0-001 · Question #492
A DBA has notified the storage administrator that a well-established, long-running database server is experiencing delays writing to /tempdb, where log files are stored. Which of the following should
The correct answer is C. Write queue length E. perfmon. To diagnose database server delays writing to /tempdb, the administrator should examine the write queue length on the storage system and use perfmon to analyze various disk I/O performance counters.
Question
A DBA has notified the storage administrator that a well-established, long-running database server is experiencing delays writing to /tempdb, where log files are stored. Which of the following should the administrator look at to help determine root cause? (Select TWO).
Options
- ARead queue length
- BReplication status
- CWrite queue length
- Dnetstat
- Eperfmon
How the community answered
(39 responses)- A5% (2)
- B8% (3)
- C85% (33)
- D3% (1)
Why each option
To diagnose database server delays writing to /tempdb, the administrator should examine the write queue length on the storage system and use perfmon to analyze various disk I/O performance counters.
The reported issue specifically concerns "delays writing to /tempdb," so focusing on the read queue length would be less relevant than examining write-specific performance metrics.
Replication status refers to the synchronization of data between database instances and is not a direct metric for diagnosing local storage I/O bottlenecks causing delays in writing to /tempdb.
A high write queue length directly indicates a bottleneck in the storage subsystem's ability to process outgoing write requests from the database server. Monitoring this metric helps pinpoint if the storage itself is overwhelmed, causing the reported delays writing to /tempdb.
netstat is a network utility used for displaying network connections, routing tables, and interface statistics, and is not relevant for diagnosing local disk I/O performance issues on /tempdb.
perfmon (or equivalent system performance monitoring tools) allows the administrator to collect and analyze various disk I/O specific counters, such as average disk queue length, disk writes per second, and average disk seconds per write. These metrics are crucial for identifying specific storage performance bottlenecks impacting /tempdb write operations.
Concept tested: Storage I/O troubleshooting for database performance
Source: https://learn.microsoft.com/en-us/sql/relational-databases/performance/monitor-disk-usage
Topics
Community Discussion
No community discussion yet for this question.