Learn more about SQL Server tools

 

Tutorials          DBA          Dev          BI          Career          Categories          Events          Whitepapers          Today's Tip          Join

Tutorials      DBA      Dev      BI      Categories      Events

DBA    Dev    BI    Categories

 

Determining who is viewing reports in SQL Server 2012 Reporting Services


By:   |   Read Comments (3)   |   Related Tips: > Reporting Services Security

Problem

Much time, effort and money can be spent on providing reports to end users, so frustration can ensue when the intended audience doesn't bother to view the reports. Also, for security purposes it is a good practice to review who is looking at reports in SQL Server Reporting Services (SSRS) in case the user no longer has a need to know the information contained in the reports.  How can we find out who has accessed SSRS reports?  Check out this tip to learn more.

Solution

As in previous versions, SQL Server 2012 Reporting Services provides us with a number of tables and views to let us see who has accessed what report and when they accessed the report.

The T-SQL query below selects from the ExecutionLog2 view in the ReportServer database.

USE ReportServer;
GO
SELECT el2.username, 
el2.InstanceName, 
el2.ReportPath, 
el2.TimeStart, 
el2.TimeEnd, 
el2.[Status],
isnull(el2.Parameters, 'N/A') as Parameters 
FROM ExecutionLog2 el2
GO

The first 13 rows output from the T-SQL code are shown below. As you can see in this image, we can see who viewed which report, when they viewed the report, and which parameters if any were passed to the report. This query itself could be used within an SSRS report and then published to the report server.

The first 13 rows output from the T-SQL code are shown below.

Using a query similar to the one shown below, we can look at the TimeEnd column to determine when the reports are being viewed. This will help us gain insight into when our processes that are generating the data behind the reports should complete. We can also look at the results of this query to determine behavioral patterns of the report users.

USE ReportServer;
GO
SELECT username, convert(varchar(25),TimeEnd, 120) as AccessTime
FROM ExecutionLog2
WHERE status='rsSuccess'
AND username='STAFF\user01' 
AND ReportPath='/Sales/YTDSalesByProductCategory'
ORDER BY AccessTime desc
GO


We can look at the TimeEnd column to determine when the reports are being viewed.

The query shown below will return the report access counts per user and report for the current month.

USE ReportServer;
GO
SELECT username, ReportPath, count(*) as ViewCount
FROM ExecutionLog2
WHERE status='rsSuccess'
AND TimeEnd>=DATEADD(mm, DATEDIFF(mm, 0, GETDATE()), 0)
GROUP BY username, ReportPath
ORDER BY username, ViewCount desc
GO


The query shown below will return the report access counts per user and report for the current month.
Next Steps


Last Update:






About the author
MSSQLTips author Dallas Snider Dr. Dallas Snider is an Assistant Professor in the Computer Science Department at the University of West Florida and has 18+ years of SQL experience.

View all my tips


 



More SQL Server Solutions




Post a comment or let the author know this tip helped.

All comments are reviewed, so stay on subject or we may delete your comment. Note: your email address is not published. Required fields are marked with an asterisk (*).

*Name    *Email    Notify for updates 


Get free SQL tips:

*Enter Code refresh code     



Friday, November 01, 2013 - 2:29:28 PM - Craig Guyer Back To Top

Mohammed, there have been a few updates to the execution log tables over various releases.  Please see the following:

Report Server Execution Log and the ExecutionLog3 View>>  http://technet.microsoft.com/en-us/library/ms159110.aspx#bkmk_executionlog2

Reporting Services LogViewer  >> http://www.microsoft.com/en-us/download/details.aspx?id=24774

I hope that helps


Thursday, September 26, 2013 - 10:19:57 PM - Mohammed Back To Top

Does this not work in SQL Server 2005. Is ExecutionLog2 something newly introduced? Thanks.


Thursday, September 26, 2013 - 1:25:02 PM - Gene Wirchenko Back To Top
It seems to me that this would be very useful to counter claims that a report is necessary. "Excuse me, but the last time this report was used was six months ago, and it is a monthly report."

Learn more about SQL Server tools