SQL-Statistics-Aggregator

Short Description:
Aggregate IO statistics to identify problem tables. Correlate disk activity with query plan nodes. Compare runs of a query over time. Export and import results for easy collaboration.

Long Description 1:
Aggregate IO statistics to identify problem tables. Correlate disk activity with query plan nodes. Compare runs of a query over time. Export and import results for easy collaboration.

Long Description 2:
Simplify SQL query tuning: Aggregate input/output (IO) statistics to identify problem tables. Correlate disk activity with query plan nodes. Compare runs of a query over time. Export and import results for easy collaboration. Stop combing through hard to read Set Statistics input/output (IO) and Set Statistics Time performance information to troubleshoot your queries. We make comparing runs over time easy and quickly so that you can spend your valuable time fixing SQL Server performance issues and less time and energy parsing lines of command results to discover how your query changes impact input/output (IO) pattern. Easily aggregate statistics input/output (IO) data: Group and aggregate Set Statistics input/output (IO) data by either table or statement. Correlate input/output (IO) activity with query plan nodes. Compare statistics over multiple runs of a query to aid in tuning and troubleshooting. Import and export statistics data: Import or paste in statistic and query plan data for analysis, or run the query directly from the tool. Export statistics and save tuning sessions to simplify sharing your work with others. Elegant design and ease of use: Download and install in a few minutes. Clean, simple user interface (UI) allows you to get up and running on a new tuning session in seconds. Integrate with SQL Server Management Studio (SSMS): SQL Statistics Aggregator is designed to launch directly within SQL Server Management Studio for optimal usability and efficient workflow. Use cases: Use this tool for a variety of performance tuning purposes including: Identifying which statement in a batch is consuming the most overall input/output (IO). Spotting tables that are creating input/output (IO) hot spots in your queries. Comparing input/output (IO) to isolate problem operations. Viewing changes to the input/output (IO) patterns.