Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Storage Resource Monitor (SRM) > SRM - Knowledgebase Articles > How IOPs information is summarized in the database

How IOPs information is summarized in the database

Table of contents
Created by Maciej Klasa, last modified by Rodim Suarez_ret on Mar 08, 2017

Views: 451 Votes: 0 Revisions: 4

Updated March 9, 2017


We are currently looking at IOPS statistics data collected from SolarWinds and how it is calculated.
SolarWinds is collecting data; for example: IOPS for a disk, every 5 minutes, then detailed statistics aggregate to hourly after 7 days, then to daily after 30 days.

What is the default calculation (max, min, average, percentile) for these statistics and can they be changed for a particular parameter such as IOPS?


SRM 6.3


All performance parameters are summarized during nightly maintenance (launched by default at 2:15am). Actuall summarization is done by launching stored procedures on the SQL server. IOPs are recorder for different elements of the array, so there is no one short answer. If you would like to see the actual SQL used to summarize, you can check following stored procedures on the SQL server:


For "hourly to daily" summarization look for procedures with name "*Statistics_HourlyToDaily" in the same location.


To access stored procedures: connect to the MS SQL database server with MS SQL Management Console, expand databases, expand SolarWindsOrion database, expand Programmability, expand StoredProcedures.


To answer your question: yes, they can be changed by modifying stored procedure, however, that can easily break SRM Orion database beyond repair. I suggest taking a backup of the database before making any changes. Any change to stored procedures will be removed by running Configuration Wizard.



Last modified