Actual Query is fast, Report is slow and does not render

I have a Report with 3 queries and when i run the queries individually they work beautifully, but when i run the report i wait 15 - 20 minutes and it doesnt bring back anything saying please wait. Also it pegs the sql server hard, when i run the report it tries to bring the server to its knees (not quite but VERY close it takes 60 - 70% of the processing power of the server until i close the report).

Each Query by itself works flawlessly, and returns all of the data within 5-10 seconds(Run through Query Analizer). Is there some funny thing that is resource intensive with actually rendering the report, it is basically just displaying the returned data, no crazy calculations. There can be a pretty big row count but nothing crazy. around 1500- 2000 on the last one
Is there a way that it is trying to run all three queries at the same time and that is killing the server?

Any help offerred is greatly appriciated

And as stated before the queries are fine and not the bottleneck, their effeciency is not the question.

Have you run all three queries together from QA with the same criteria that is taking a long time?
Can you post the queries?
Can you use 3 stored procs instead?

|||as i said it isnt the actual query it is the time it takes to create the report

I ran all queries involved in this report in a total of 5 minutes and that includes the amount of time to switch between the queries and enter the value of the parameter.

The report itself took 46 Minutes, nothing different, i actually ran the queries from the actual query used in the report when i achieved the 5 minute mark

Does something in SP2 fix this?|||Sorry - late to this POST
You have to install SP2 and I think there may be a "HotFix" as well --
Also, is there a Document Map you are creating when generating the report? I have had situations where I created a Document Map with a SQL table of about 400,000 records and I got inpatient and started to select a hyperling on a row of data that was displayed - but the entire worker process was not completed and my machine "hung" everytime!
Then if NO DOCUMENT MAP, then is there a problem with the length of the parameters defined within the stored procedure - As you know there is no length to define within MSRS - but if you enter a 5 byte field in MS RS and the resulting parameter in the stored procedure is 2 - then problems!
But nevertheless, I havfe not seen this behavior in MS RS and I have used a lot!
Best regards,
]
Joe|||What does the document map do? Does it make the creation of the report more efficient?
I am having this problem with many reports.
I am not using a stored procedure, but can you expand more on the thought of parameter size? why would it change?
What can you do to prevent it?