That report is merely running queries against the database box. All this data can be easily queried once you write the code. You can then schedule that in a SQL job for execute, or if needed, create a SSIS package that can do even more. Pretty much anything that you want.

I do not think there is a way to schedule the packaged queries that make up these simple reports. But they are nothing more than a query that runs on SQL Reporting Services in SSMS.

I would suggest that you keep this data in a DatabaseMaintenance database for historical reporting. And that will keep the transactions low on the database(s) involved. The data will be queries only once, gathered and inserted into the proper tables. Then SSRS can use the DatabaseMaintenance database as one of the data sources. You could use any front-end that you like. Or you can create another SSIS Package that send this out to a select group. I would use a web based front-end so that they can look at the data anytime they want, and over and over without straining the database box.

Andrew SQLDBA