Hi All I am having a problem with SSRS reports which I hope you can help with. We have a web application which contains a couple dozen reports built using SSRS. In order to do a new release I first deploy the web application and the SSRS reports to our pre-production server for testing. Whilst testing is going on, developers are making further changes to some of the reports and also the the database structure. My problem is that when I want to move the new release from the pre-production server to the production server, I can copy the application but not the SSRS reports. So my only choice appears to be to deploy the SSRS reports from a devlopment machien directly to the production server. This is clearly going to cause me problems as those reports may have been further developed and the database structure may have changed sine deploying the application to the pre-production server so I am effectly releasing untested reports directly to the production srever. So my quesiton is: How can I copy my SSRS reports from the pre-production server to the production server? Is there another way of dong this? Regards Smeat

yes.....can we just get a link to this tool pinned?www.sqldbatips.comhas a tool called Reporting Services Scripter 2.0.0.81.you point it at RS, set the options, it creates the script + files2.global find replace in the files i.e. change servernames3.run scriptI suggest you try this in some kind of development environment first to understand all the different options this tool has

Thanks for the info. One of our developers is checking this out. Smeat

One way of accompishing your goal will be using a version control software like Visual Source Safe. Here's the scenario. 1. Developer develops version 1 of report andcheck in Visual Source Safe. 2. Designated person (configuration administrator) pushes version 1 of report to pre-production environment. 3. Report is tested by QA group & users in the pre-production environment. 4. QA groupand/or users discover errorsand/or updates to be done by developerson version 1 of the report. 5. Developer implements updates and fix errors found on version 1 of the report &check in new version intoVisual Source Safe (version 2). 6. Repeat step 2 but this time will be version 2 of the report. 7. Repeat step 3. Move to next step (step 8)if QA group & users are OK with updates; otherwise, repeat step 5 - 7 8. Designated person (configuration administrator) pushes final version of report to production. I hope this helps.

I wrote this small little tool to help me do the same http://code.google.com/p/reportsync/ It can copy reports(or selected folders) from a source server to destination server. You can also download to and upload from a local directory. Datasources are automatically attached if they are at the same location(same name) on the destination server.