Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

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: 351 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