Deploying SSRS Reports

Question

Deploying SSRS Reports

H4K

Hall of Fame

Points: 3374
More actions
October 7, 2010 at 1:27 am

#239489

Hi All,
I have to often deploy more than 1000 reports on the report server.
So i wanted to know what are the different ways to deploy the SSRS Reports on RS ??
Regards,
Amar Sale
BI Developer
SSRS, SSIS, SSAS, IBM Cognos, IBM Infosphere Cubing services, Crystal reports, IBM DB2, SQL Server, T-SQL
Please visit... ApplyBI

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Luke L SSC-Dedicated Points: 35547 More actions · Answer 1

Really, you're adding 1000 reports at the same time? Is this because you are setting up new clients with the same reports or because you make 1 change and redeploy the entire solution? If it's the second, why not just right click on the report you changed and click deploy. It will only deploy that 1 report.

If indeed you are doing 1000 at the same time, you might take a look at rs.exe (it's a command line tool which comes with SSRS) or the RS Scripter available here.

-Luke.

To help us help you read this[/url]For better help with performance problems please read this[/url]

Doug Lane SSCrazy Points: 2118 More actions · Answer 2

Just curious, have you looked into linked reports? If you have 1000 reports, there's probably a use for linked reports in there somewhere.

Link:

Linked Reports on TechNet

Cody Konior SSCarpal Tunnel Points: 4827 More actions · Answer 3

I have a hundred or so reports that need to be deployed into different folders, and copied across multiple servers (development, testing, production) which means that the BIDS deploy function would really suck.

So I organised my solution with multiple projects and the appropriate folder names that I wanted to exist on the report server.

Then I scripted RS to iterate through the solution structure, create the folders, deploy the reports one by one, and fix the data source references. I call the RS script from a batch file that runs it for each server I want to deploy too. The batch file prompts for which server number (or all), and a report name (blank = deploy all, otherwise it will quick deploy that specific report to all selected servers, which is great for emergencies or if you just made a small change and don't want to redeploy everything).

The same script can also detect errors in the reports.

For example, for each parameter in the report I put a DECLARE statement at the top of the T-SQL in the query so it can be cut/pasted into SSMS for debugging purposes later, eg: DECLARE @InvoiceNumber blahblah as NVARCHAR(MAX) = '1235'. Sometimes you even cut and paste it back from SSMS to BIDS if you've made a change.

The problem with this is that you have to comment out the DECLARE statements whenever you deploy the report live, and as fate would have it, after you've been doing it for months on end you're going to mess it up and deploy a report with an uncommented DECLARE in it. So I added a little RegEx checking to the deployment script to avoid deploying reports that have any uncommented DECLARE statements in them 😉

Personally I think it's a kick-butt way of doing things. The idea could be extended to detect and re-deply only changed reports, or keep a deployment history, but that wasn't necessary for my purposes.