I work for an organization whose internal reporting consists of about 25 source databases across a dozen or so servers. In SSRS we have two Solutions, each containing a few thousand reports. Every now and then, some comic genius in the infrastructure team will advise us that they're renaming a server instance, or moving a DB onto a different server. Obviously this breaks all the affected reports (mainly where linked servers come into play - which is a lot) and we have to go through each affected rdl and fix and deploy. Manually. Or so it would seem. The latest is that the "look and feel" police have told us that the organization logo is changing. It's embedded in every report. How do others handle mass "fix and deploy" situations?
What I do with the datasources is use a shared datasource, that way when a database name or server name changes I just have one change to make. By using a shared datasource when multiple reports use the same datasource you can make a single change to update the database name or server name. As for the logo I am not sure how easily that can be updated if the size of the logo is changing. If the logo is the same size I would think you could simply name the image file the same name as the old logo and replace it. I have tested that though.
Have you considered using PowerShell:
http://timbenninghoff.com/archive/2010/03/creating-a-reporting-services-rdl-from-powershell/ It might not be a quick fix right now but something that can be built into a good solution. I don't mess with Reporting Services much but a quick search on Google showed there are options available to interact with RS with PowerShell in deploying reports. I would imagine there has got to be something out there on being able to modify them against multiple servers.