How does Reporting Services handle multiple report requests simultaneously?

ex. I have 800 users that all run one report at the exact same time or they
all run different reports at the exact same time.

Does the report server que up the reports in an arbitrary order?
Do all the reports process without any issues?


Thank you,

If part of your concern is efficiency keep in mind that you have a lot of
options for report processing. For instance, you can run a report at night
and then when a user requests the report it has already been created. You
can also set for a report on how long it is cached for other users to use
the same report without re-running it. One other thing you can do to run
well under heavy load is to take advantage of connection pooling. Report
Server is an asp.net application so just like any other asp.net application
that goes against a database you should try to use connection pooling. The
way to have this work with RS is to have a specific username that is used to
retrieve your data. What I do is setup a read only user for RS. This means
using mixed mode authentication with SQL Server. This allows RS to make good
use of connection pooling.

--
Bruce Loehle-Conger
MVP SQL Server Reporting Services

[quoted text, click to view]

Hi

Yes, RS is true multi-user. Generally, RS is not the issue. Blocking and
locking on inefficient or not optimal queries cause the trouble with high
loads on the SQL Server.

The only way for you to find out is to test.

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

[quoted text, click to view]