Let's say you have a suite of reports that require publishing. To deploy
these server side so that others can view, developers will open the Reporting Services
Visual Studio project in BIDS, confirm the properties of the project point to the
appropriate SSRS server and folder locations, then deploy the required objects.
Great. But what if you need the reports to be promoted into a managed
area such as User Acceptance Test (UAT) or Live/Production. That is, the deployment
of all report objects is to be handed over to a release team who aren't familiar
much less have access to Visual Studio. The required steps include one
or more of the following
- Give the developers update access to UAT and Live/Production to deploy via Visual Studio
- Table unneccessaily detailed deployment instructions for the release team to manually
upload each of the desired report objects
- Carry out the task of creating data sources, and uploading each desired object manually
- If reports, shared data sets, and/or data sources are in separate folders, each
report needs to be synchronised with the corresponding data set and data source,
and each data set needs to be synchronised with the corresponding data source
As well, you may have a Continuous Delivery/Integration (CI) environment that is updated
via an automated process. Neither the Visual Studio deploy process nor
the manual upload process is appropriate.
Basically there is no option but to automate the deployment. This can be done via
interracting with the rs.exe command line tool or via calling the WebService that
comes with the SQL Server instance installation.