Reporting Services Performance

Hi,

I'm just wondering if anyone else has had any problems with reporting services when generating reports.

I have a rather large report (approx 5000 rows) and to be fair there are alot of links to other tables. However it takes 5-10 minutes to generate this report.

If I manually pull the data from the database, perform the aggregations and all the table joins, it takes under 10 seconds to complete and I seriously doubt that rendering the table to put the data in takes 10 minutes to do.

Any Ideas?An update on this,

I just tried creating a report without all the information in the other tables, so the report is now taking 5128 rows from one table and displaying all the columns. This took 5 minutes to generate.

Again any Ideas on why this is taking so long?|||

Do all significant data processing on the server, particularly joins/unions/selections/projections.

Limit the report engine to data processing that's easy for it to do without additional roundtrips to the server, such as running totals, grouping, subtotaling, etc.

I'll bet your 5 minute report will become instantaneous by pushing the data processing to the server, where it is best handled. Views and stored procedures are your friends.

This approach also reduces the dependency on the report writer, so that you can use other report engines to render the same report data regardless of the capabilities and quirks of their client-side data engines.

|||

I have the following task to investigate: which server will need more resources at the time of reports execution using Reporting Services 2005

In a standard deployment you will have two servers: A. Report Server

B. SQL Sever Database

When using enbedded code / Expression in a report: example: Sum, Count, etc. Who will execute this action? It is the Report Server or the SQL Server?

The main idea is to determine who will need more resources in order to have the best performance in the reports execution.

Thanks