SSRS report font problem on deployed reports

I have similar problem. I created "banks" of shared schedules to handle this.

For example

I have 1 "bank" setup to run at 6am another to run at at 6:05 etc. Then I make sure that the reports are balanced across each "bank".

Another option to look into is Resource Governor (Requires sql server 2008). It won't queue up the jobs; but it will allow you to ensure that they don't bog down the server:

[Resource Governor on BOL1

Copying reports is pretty easy if you have the original RDL/SMDL files; simply redeploy/upload it again, and change its name/location/datasource.

If you don't have the original RDL/SMDL files, you'll need to extract these from the report server and redeploy. The easiest way to do this is via an rs.exe script.

The following describes how to copy reports from one server to another, but the same principles apply when copying reports etc. to the same server (from http://msdn.microsoft.com/en-us/library/ms159720.aspx):

You can write scripts that duplicate a report server environment on another report server instance. Deployment scripts are generally written in Visual Basic and then processed using the report server script host utility. The following list describes the steps for migrating reports from one server to another.

1. Set your script variable to the URL of the source report server.
2. Use the GetReportDefinition and GetProperties methods to retrieve the report definition and the properties of the report.
3. Set the URL to point to the destination server.
4. Use CreateReport method, passing the properties returned from GetProperties and the report definition returned by GetReportDefinition.

Once you've copied the reports, you can change the data source for the reports and the model (assuming you haven't done it programmatically via the RSS script):

• In the Report Manager, click "Show Details" in the toolbar
• Browse to the folder containing the object you wish to change (report or model)
• Click its Properties
• In the Data Source page, change the data source details to point to the new database (changing the credentials too, if needed)

If they're using a Shared Data Source, it'll be easier to leave them as they are and change the server it references, without touching the reports and model, so change the second point above to "Find the shared data source they reference"