Case Scenario: Deploying and Scheduling SSRS Reports

You are the SQL Server Reporting Services (SSRS) administrator for the Adventure Works bicycle company. Your end users complain that the reports they are using are sometimes replaced with newer versions without their knowledge, and the newer versions often do not work. You also noticed that some advanced end users have created subscriptions to the reports. Some of those subscriptions run long reports during peak hours, creating performance bottlenecks on the production server. Some less advanced end users want to subscribe to some reports as well. Different users have asked for different rendering formats, and the report files have to be delivered in different folders.

1.	How can you prevent uncontrolled upgrades of the reports?
2.	How can you control execution times of subscriptions?
3.	How can you prepare subscriptions with different parameters for different users with minimal effort?