![]() Preferred: SQL Nexus Scenarios to use: performance analysis, best practice recommendations, bottleneck analysis, blocking, and top queries. Preferred: SQL LogScout Use scenarios "GeneralPerf," "DetailedPerf," or "LightPerf." - Alternative: PSSDIAG Use scenarios "General Performance," "Detailed Performance," or "Light Performance." Extended Event (XEvent) trace captures batch-level starting/completed events, errors and warnings, log growth/shrink, lock escalation and timeout, deadlock, login/logout - List of actively running SQL traces and Xevents - Snapshots of SQL DMVs that track waits/blocking and high CPU queries - Query Data Store info (if that is active) - tempdb contention info from SQL DMVs/system views - Linked Server metadata (SQL DMVs/system views) - Service Broker configuration information (SQL DMVs/system views) Alternative: SQL Nexus Scenarios to use: performance, latency, health, and best practices. Preferred: AGDiag Scenarios to use: Analyze failover and failures. Preferred: SQL LogScout Use scenario "AlwaysOn." - Alternative: TSSv2 Use scenario "SQL Base." - Alternative: PSSDIAG Use custom diagnostic "Always On Basic Info." Cluster logs - Event logs - System Monitor (Performance monitor logs) - SQL Server error logs - SQLDIAG XEL files - AlwaysOn Health session XEL files - System Health session XEL files - Extended Events for AG data movement - DMV and Catalog view snapshots for AG ![]() ![]() The article details various troubleshooting scenarios and shows the corresponding log collection and log analysis tools. This article summarizes the diagnostic tools that SQL Server product support engineers have been using. These tools are available to use publicly. Microsoft Product support for SQL Server hybrid uses troubleshooting tools to help customers collect logs and narrow down technical issues.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |