【正文】
erver Activity History has multiple sections: SQL Server v. System performance for: %CPU Utilization, Memory Usage, Disk I/O Usage, Network Usage SQL Server Waits: Logging, Latches, Locking, CPU, Network I/O, Buffer, … SQL Server Activity: Batch Requests/sec., Logouts/sec, SQL ReCompilations/sec, User Connections, Transactions, … Mar2022 21 Microsoft Developer amp。 Platform Evangelism Module Overview Management Data Warehouse Performance Data Collection ? Performance data collection ponents ? System collection sets ? Userdefined collection sets ? Reporting Centralized Administration: Bringing it all together Performance Data Collection and Reporting Mar2022 22 Microsoft Developer amp。 Platform Evangelism Centralized Administration Configure a robust, centralized server as: ? Configuration Server ? Centralized Master Server – setting all of the servers of a Configuration Server as targets ? Centralized Performance Data Collection (MDW) ? Centralized Policy Store Always use a Management Data Warehouse that’s centrally located (so that you don’t get caught in collecting performance metrics on collection itself) Downside to this is that reports are accessed locally despite the central MDW – consider creating custom reports at the MDW to correlate the relationship between servers Mar2022 23 Microsoft Developer amp。 Platform Evangelism msdb Centralized Administration Performance Data Collection and Reporting Mar2022 24 Microsoft Developer amp。 Platform Evangelism Centralized Server Master Server (MSX) Configuration Server Policy Store for centralization Management Data Warehouse Database Mirroring Witness Reporting Server “Standard” Performance Data Collection Reports Generated these locally – at the server where collection is defined Centralized Reporting “Custom” Performance Data Collection reports can be written on a centralized management data warehouse for better servertoserver correlation mdw Policies Configuration Server MSX Mar2022 25 Microsoft Developer amp。 Platform Evangelis