abigail.tomlins (8/20/2014)
HiyaThe report is calling a stored procedure so speed wise it should be ok, I'm wondering whether it's just the amount of data it's trying to retreive as it's quite alot?
While using a stored procedure may make it easier to optimize teh SQL, in reality, a stored procedure vs. parameterized sql doesn't really make a difference in performance. You really need to take a look at the ExecutionLog3 view, as I mentioned in my first post to determine what part of the report run is taking the most time. A query like this:
SELECT
EL.ItemPath,
EL.UserName,
EL.ExecutionId,
EL.RequestType,
EL.Format,
EL.TimeDataRetrieval,
EL.TimeProcessing,
EL.TimeRendering,
EL.Source,
EL.ByteCount,
EL.[RowCount]
FROM
dbo.ExecutionLog3 AS EL
is a decent starting point as you'll have some actual metrics to work from.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question