This, and the list of disks that contain SQL Server databases (from the SQL Server | Databases drilldown), may help to determine if SQL Server is generating the I/O. The Windows Server | Disks drilldown | Logical Disk Activity page to see which disk(s) are being hit the hardest.If SQL Server is not generating a lot of I/O activity, then it is most likely being caused by some other Windows process, or by Windows itself. The SQL Server IO graph shows the rate (pages per second) for each type of I/O that SQL Server is performing. The SQL Server | SQL Activity drilldown | Summary page to see if SQL Server is generating high amounts of disk activity.When this alarm is raised you should look at: The occurrence of this alarm does not necessarily indicate a problem with SQL Server instance, however SQL Server (and anything else on the machine that performs disk I/O) will feel the impact of slower disk throughput. Note: Since this is a Windows-based alarm, it can be impacted by I/O that was performed by non-SQL Server processes. ![]() Collect additional diagnostic information.Virtualizd Memory page (Hyper-V server host).Virtualized Memory page (VMware server host).Virtualized CPU page (Hyper-V server host). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |