A list of gripes about features I feel are missing from Microsoft SQL Server Reporting Services 2008 R2.
1. The ability to throttle an individual report
Report Builder 3.0 makes it easy to create reports which is great and encourages “self-service” reporting. Business users creating reports hooray!
Unfortunately, there is no way to prevent damage to a production environment caused by a poor-performing report. If someone creates a report that consumes 2 GB of memory on the SSRS server there is no way to prevent that report from running short of disabling the datasource or removing the report entirely.
There needs to be a way to set a memory or time limit in “Manage Processing Options”.
2. Error handling for failed subscriptions
Subscriptions are such a great idea and users love them. However, if a subscription fails.. what happens?
Answer: nothing. Essentially, what you can do is click “Manage Subscriptions” to check the “Last Results” field. This assumes you know which report has subscriptions.
There needs to be some way to view subscriptions in a site collection, detect failed subscriptions, and provide the ability to (automatically) re-run failed subscriptions.
Bonus: if a user creates a subscription and then their account is deactivated (example: leaving the company), their subscriptions will fail. Ouch!
3. Logging (AKA the ability to troubleshoot)
Troubleshooting an issue? Good luck using the logs to figure it out. Which logs do you want to look at? SharePoint logs? IIS logs? SSRS logs? Event viewer? Database logs?
Assuming you’re able to gather all of that information up.. it is impossible to correlate a specific run together. I think in the newer version of SSRS there is a correlation ID.. so maybe someone can confirm.
Also, there needs to be a detailed log for Subscriptions. A “Last Results” field that gets overwritten on subsequent runs is next to useless.