Ever had a manager standing over your shoulder, wanting to know why an instance is running slow or if it can handle additional workload? What information would you use to answer these questions? If only you knew what performance metrics to collect and had them for your existing instances to answer these questions.
In this session, we will discuss sp_whoisactive and Query Store. Then we will be combining three open source tools – Telegraf, InfluxDB, and Grafana – into an inexpensive system that collects performance metrics you can use to troubleshoot issues and answer important questions about your SQL Server instances, including your Linux SQL Server instances. We will learn what metrics to collect, how to use the tools to collect performance metrics and then we’ll put it all together in an interactive dashboard for easy visualization.
Attendees will see how easy it is to get good performance data and visualize in an interactive way and combine with other tools to troubleshoot issues. For an example, we will combine this solution with Query Store and/or sp_whoisactive to find a problem that occurred on a system and caused me to get my nap interrupted on a Saturday.
Get full session notes here: https://groupby.org/conference-session-abstracts/using-open-source-products-to-collect-performance-metrics/
Every time you see a Columnstore Index getting involved in the execution plan, do you realize that there are whole execution plans behind those Index Scans ? Did you ever ask yourself, what are those strange and weird HT_* waits stand for ? Why do we wait for seconds/minutes for something like HTBUILD while it seems that nothing happens ? Why do we have a ROWGROUP_VERSION wait on one server, while the other allows queries to run faster ?
This session focuses on answering those question - to help you understand the reasons and the conditions behind every single available wait for the Columnstore Indexes and the Batch Execution Mode.