How well is SQL Reporting Services is scalable to handle deadlock -- sql server reporting services

Keerthi Pavan
12/5/2005 10:41:02 PM

Hi,
We are developing a Reporting application,where we propose to use an
already existing SQL 2000 Reporting Service instance to place our new
reports.
What i mean from this is,There already exists a Reporting application which
uses a .Net Window service to publish reports(7000 Reports/Day) onto a
installed instance of Reporting Service. With our new application we will use
a different Window service but want to place reports(around 5000 reports/day)
on same existing SRS Instance.

We would like to know if we are going to face any deadlock contention issues
when both of backend Window service components try to acquire locks of SRS
Report manager during publish time.Is SRS designed to handle this robustly??

Daniel Reib [MSFT]
12/6/2005 11:21:48 AM

So are you saying you are currently publishing 7000 reports a day and want
to now publish an additional 5000? Report server should be able to handle
this kind of a load, however Publishing can be a fairly CPU intensive
operation and you may want to look into adding some more machines to handle
the load and give faster response times.

--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.

[quoted text, click to view]

sql server reporting services : How well is SQL Reporting Services is scalable to handle deadlock