Reporting Services - max simultaneous reports 1

[dddenney]

I was wondering if anyone knew if there was a limit on the number of reports run through Reporting Services (both scheduled and user run), before it either starts queueing reports or something else. Or is there even a limit (other than resources)?

This is for Sql Server Standard 2005 SP2.


Thanks in advance,

Dan

 

[JayKusch]

That is kind of a loaded question - lol.

Depending on how your environment is set up depends on the "queueing" up.

Of course we know the backend to RS is SS so (in most cases) and depending on if this is a single node config or a NLB (Load Balanced environ w/ many nodes) the queueing is more or less the time it takes for the SQL code to generate the record set needed to report on.

SO we could have an issue where there is a single node and some very poorly written code that could take a long time to process or it could be a case of code locking and blocking other "report" threads for getting resources to a general "heavy" loaded system that is being used as an OLTP AND an OLAP as most servers I have seen are - lol.

So the "queueing" questions is multi-tenant.

But at least we have a base for discussion.

What are you seeing and how is your environment carved out?

Thanks

J. Kusch

 

[dddenney]

Thanks Jay.

Most of our reporting services reports are actually hitting an Oracle database on the backend.

One of our report developers thought that Reporting Services would only allow so many active reports to run at the same, before reports started getting queued pending completion of other reports. I thought that in theory you could run any number of reports, but that you were only limited by resources (both hardware and on the backend).