May 3, 2012 at 11:34 am
We have a reporting services instance in our DMZ. It's used extensively in an ASP.net web application sitting on the same server in the DMZ. Users are complaining of slowness. I see that the following query is executed from Reporting Services around 3000 times an hour.
Procedure: ReportServer.dbo.ObjectExists
*/
CREATE PROCEDURE [dbo]
.[ObjectExists]
@Path nvarchar (425),
@AuthType int
AS
SELECT Type,
ItemID,
SnapshotLimit,
NtSecDescPrimary,
ExecutionFlag,
Intermediate, [LinkSourceID]
FROM Catalog
LEFT OUTER JOIN SecData
ON Catalog.PolicyID = SecData.PolicyID
AND SecData.AuthType = @AuthType
WHERE Path = @Path
This is actually the worst performing query on the database server and the worst coming from the application server. Any way to reduce the number of executions?
As a side not if the include client statistics in a test execution from management studio it seems to indicate over 1 MB returned to the client, even though I expect the data returned should be much less.....
The firewall admin here indicated that over 115 GB is crossing the firewall daily from the application server and I suspect mostly related to Reporting services. Any advice is appreciated!
Cheers,
May 3, 2012 at 11:50 am
FYI - It's reporting services 2005.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply