October 28, 2014 at 7:58 am
Pardon my ignorance of SSRS. I've never used it before and need to know how to "promote" reports.
We have a separate Dev, Staging, and Prod server, each with SQL Server and SSRS up an running.
My question is, is there a way to "promote" reports from Dev to Staging to Prod using only "native" tools OR some trickery from the Command Prompt or using PowerShell? I've been looking and haven't found a reasonable solution. We'll need to "promote" possibly "dozens" of reports and all the methods I've seen so far only handles one at a time. Command line or PowerShell is certainly an OK thing for us.
The goal is that I'm trying to avoid having to use products like TFS (which would require more expense) or products like ReportSync, which is cool but is an unsupported .EXE. We're also trying to avoid the expense of using the good code the companies such as Pragmatic Works offer. We're looking for something that we can modify if we need to someday in the future.
Thank you very much for your help on this.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2014 at 8:52 am
Thanks, ol' friend. Great minds think alike. I just found the following example that uses RS and, at first blush, looks fine. Combined with the official link that you provided, I think I just might be able to pull this off in a relatively simple fashion. I might even be able to avoid the VB script. Thank you so very much for the quick response.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2014 at 9:19 am
As a bit of a sidebar, I read some of the comments that follow that article and some dude said the performance of RS "sucks". When I read that it took a mere 30 minutes to deploy 300 reports and offered no alternative, my immediate thought was "Dude, you can't be serious".
It's a good article but I do wish the author of that article would have taken the time to respond to some of the posts that indicated some trouble. Guess I'll find out any caveats on my own. 😛
Thanks again, Gianluca. I appreciate the help you've given on this. I'll let you know how it all works out.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 28, 2014 at 9:26 am
I used it a couple of times and it worked flawlessly for me.
I migrated a 2008 to 2012 and it had hundreds of reports. It took a couple of minutes, no more.
I hope it fits your needs.
Actually, deploying reports from dev to prod could also be done in Visual Studio, but I have no first hand experience on that.
-- Gianluca Sartori
October 28, 2014 at 9:26 pm
That's great amplifying information. I'm also glad to see that you can also promote data sources with the understanding that you might need to change some credentials. I'm even happier to see that you have the choice of NOT migrating data sources. That was one of my goals. Using careful naming conventions in the reports themselves, we want to be able to promote the reports using all existing data sources.
This very well could be the key to me creating the automated bullet that I've been looking for. Thank you, again!
--Jeff Moden
Change is inevitable... Change for the better is not.
October 29, 2014 at 7:11 am
We used RSScripter, by Jasper Smith, and it worked really well for us. Can't find an original link, but Google gives many results and reviews.
Jared
CE - Microsoft
October 29, 2014 at 6:31 pm
Thanks for the tip. I found the following website on the subject.
http://execsql.org/rs-scripter-tool-handy-tool-to-create-deployment-script-for-reporting-services
One of the steps is to provide a path the RS.exe file so I think it's purely an interface to that program. That's not a bad thing. That will allow people not familiar with the Command Line or VBS to easily get the job done.
Thank you, Jared.
--Jeff Moden
Change is inevitable... Change for the better is not.
October 30, 2014 at 9:17 am
It's so automatic that I had to think hard as to whether I'm mis-reading something in your post, but this is what we do to deploy reports.
We set up project configurations and deploy by right clicking either the individual report or the whole project in visual studio (BIDS)
In solution explorer window:
right click the solution (tip, set tools, options, projects and solutions to have Always show solution ticked) - it's the top item of the lot
Choose configuration manager and set up the three different configs. dev Test and Live in our case.
Then right click the project (below solution) and choose properties and set up your target report server details, datasource folder, overwrite datasources etc for that configuration. Save and repeat for each configuration.
By selecting the correct configuration property for the solution, you can then right click one or more reports (multi-select) to deploy to the correct server with a click.
If I'm copying a load of reports from one server to another I use the rsscripter tool
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply