AverageExecutionTime: how much time the report takes, on average, to run.TotalExecutionTime: how much time has elapsed in running that report.ExecutionCount: the number of times the report has been run.RequestType: interactive (run on the user interface), subscription (run automatically), refresh cache (refresh data).= 2 THEN ‘Refresh Cache’įROM ReportServer.dbo. The purpose is to highlight how much usage and what type of usage each report gets as well as providing some additional overview data on that reports. It also provides a set of data and information around those reports providing overall usage data for the period. This is an overview, summary data extract of the SSRS instance with the main purpose of providing information on the reports that are accessed on the server. I’ve provided a few reports that I’ve found useful here. The ReportServer database has a number of other tables such as the Catalog table, that holds details on the report itself, that can be brought in to make the report more detailed. Data is stored in a table called ExecutionLogStorage and is queryable like any other data source. The good news is that this has been thought of and that data is stored in a queryable data store on the SQL Server that has SSRS installed. However, I found myself pushing out report after report and wondering how useful were these reports? And who was using them? And how often? Sure you’d know a report was important if it broke or had an issue and the help desk requests would roll in, but how does one know day to day usage of reports that are not having issues? That report built four years ago, have you not heard about it because it is churning along doing it’s business value-add thing? Or has it not been used for months and is just cluttering up the system? Or worse it has become not useful, but no one has requested a change? Execution Log Storage on Report Server SQL Server Reporting Services (SSRS) is a fantastically useful product that enables a clean and clear interface for end-users to pull data out via a clean web interface (particularly since SQL Server 2016 updates).

Rising tide interactive twitter