Hi all, I have a problem to solve for synchronizing report objects between multiple instances of reporting services. Our production data is distributed via replication from our head office to database servers at our remote offices. Likewise, we want to have an instance of reporting services co-located with each of the databases and therefore will be installing reporting services instances at the remote offices. I would like to optimize for efficiency in keeping the report objects in sync, minimizing data transfer and as little manual intervention as possible so as to avoid mistakes. I have come up with several approaches to acheiving the SSRS replication I seek: a) Use a scale-out deployment. This would mean creating multiple instances of the reports to account for the multiple DataSources I would need to configure, since I can't parameterize the DataSource in a linked report. b) Manually replicate reports to each of my deployments using BIDS/SSMS. This would involve a ton of admin as all objects should be kept in sync. c) Write RSS scripts to handle the synchronization of the servers. This shouldn't be too hard given that the webservices should play nicely with such a solution. It might take some effort to write the object comparison routine. d) Have the replication engine take care of the replication of report objects between the servers. If I sync up the encryption keys, could I set up replication on all the tables I need synchronized and just be done with it? This would be my favored solution but I'm not sure it is possible. Any ideas and suggestions would be appreciated. Thanks,Calvin

I would go with the option c) or use the web farm scenario where you can actually share the report server database with several web servers. If they have a connection to the report server database that should be fine for you.HTH, Jens SUessmeyer.---http://www.sqlserver2005.de---

I know this is already marked answered, but I figured I would put this up here since I ran across it today, probably would do what you neededhttp://www.sqldbatips.com/showarticle.asp?ID=62it worked for me at least

Sharing the database isn't the best of ideas. Your database then becomes your single point of failure. Sharing the database would take away a lot of advantages of distribution. (c) is the best options. RSS scripts would help a lot. I wrote a small utility to help sync reports across two servers. It is helpful if you if you ever have to sync manually. http://code.google.com/p/reportsync/