I Have created an SSRS Report for retrieving 55000 records using a Stored Procedure. When
executing from the Stored Proc it is taking just 3 seconds but when executing from SSRS report it is taking more than one minute. How can I solve this problem?
The additional time could be due to Reporting Services rendering the report in addition to querying the data. For example if you have 55,000 rows returned for the report and the report server then has to group, sort and/or filter those rows to render the report then that could take additional time.
I would have a look at the way the data is being grouped and filtered in the report, then review your stored procedure to see if you could offload some of that processing to the SQL code, maybe using some parameters. Try and aim to reduce the the amount of rows returned to the report to be the minimum needed to render the report and preferably try to avoid doing the grouping and filtering in the report itself.
I had such problem because of parameters sniffing in my SP. In SQL Management Studio when I run my SP, I recreated it with new execution plan (and call was very fast), but my reports used old bad plan (for another sequence of parameters) and load time was much longer than in SQL MS.
in the ReportServerDB you will find a table called ExecutionLog. you got to look up the catalog id of your report and check the latest execution instance. this can tell you the break-up of the times taken - for data retrieval, for processing, for rendering etc.
Use the SSRS Performance Dashboard reports to debug your issues.
Archaic question but because things like that are kinda recurring, my "quick and dirty" solution to improve SSRS, which works perfectly on large enterprise environments (I am rendering reports that can have up to 100.000+ lines daily) is to properly set the InteractiveSize of the page (for example, setting it to A4 size -21 cm ). When InteractiveSize is set to 0, then all results are going to be rendered as single page and this literally kills the performance of SSRS. In cases like that, queries that can take a few seconds on your DB can take forever to render (or cause an out of memory exception unless you have tons of redundant H/W on your SSRS server).
So, in cases of queries/ SP's that execute reasonably fast on direct call and retrieve large number of rows, set InteractiveSize and you won't need to bother with other, more sophisticated solutions.
I had a similar problem: a query that returns 4,000 rows and runs in 1 second on it's own was taking so long in SSRS that it timed out.
It turned out that the issue was caused by the way SSRS was handling a multi-valued parameter. Interestingly, if the user selected multiple values, the report rendered quickly (~1 second), but if only a single value was selected, the report took several minutes to render.
Here is the original query that was taking more than 100x longer to render than it should:
SELECT ...
FROM ...
WHERE filename IN (#file);
-- #file is an SSRS multi-value parameter passed directly to the query
I suspect the issue was that SSRS was bringing in the entire source table (over 1 million rows) and then performing a client-side filter.
To fix this, I ended up passing the parameter into the query through an expression, so that I could control the filter myself. That is, in the "DataSet Properties" window, on the "Parameters" screen, I replaced the parameter value with this expression:
=JOIN(Parameters!file.Value,",")
... (I also gave the result a new name: filelist) and then I updated the query to look like this:
SELECT ...
FROM ...
WHERE ',' + #filelist + ',' LIKE '%,' + FILENAME + ',%';
-- #filelist is passed to the query as the following expression:
-- =JOIN(Parameters!file.Value,",")
I would guess that moving the query to a stored procedure would also be an effective way to alleviate the problem (because SSRS basically does the same JOIN before passing a multi-value parameter to a stored procedure). But in my case it was a little simpler to handle it all within the report.
Finally, I should note that the LIKE operator is maybe not the most efficient way to filter on a list of items, but it's certainly much simpler to code than a split-string approach, and the report now runs in about a second, so splitting the string didn't seem worth the extra effort.
Obviously getting the report running correctly (i.e. taking the same order of magnitude of time to select the data as SSMS) would be preferable but as a work around, would your report support execution snapshots (i.e. no parameters, or parameter defaults stored in the report)?
This will allow a scheduled snapshot of the data to be retrieved and stored beforehand, meaning SSRS only needs to process and render the report when the user opens it. Should reduce the wait down to a few seconds (depending on what processing the report requires. YMMV, test to see if you get a performance improvement).
Go to the report's properties tab in Report manager, select Execution, change to Render this report from a report execution snapshot, specify your schedule.
The primary solution to speeding SSRS reports is to cache the reports. If one does this (either my preloading the cache at 7:30 am for instance) or caches the reports on-hit, one will find massive gains in load speed.
Please note that I do this daily and professionally and am not simply waxing poetic on SSRS
Caching in SSRS
http://msdn.microsoft.com/en-us/library/ms155927.aspx
Pre-loading the Cache
http://msdn.microsoft.com/en-us/library/ms155876.aspx
If you do not like initial reports taking long and your data is static i.e. a daily general ledger or the like, meaning the data is relatively static over the day, you may increase the cache life-span.
Finally, you may also opt for business managers to instead receive these reports via email subscriptions, which will send them a point in time Excel report which they may find easier and more systematic.
You can also use parameters in SSRS to allow for easy parsing by the user and faster queries. In the query builder type IN(#SSN) under the Filter column that you wish to parameterize, you will then find it created in the parameter folder just above data sources in the upper left of your BIDS GUI.
[If you do not see the data source section in SSRS, hit CTRL+ALT+D.
See a nearly identical question here: Performance Issuses with SSRS
Few things can be done to improve the performance of the report which are as below:
1. Enable caching on the report manager and set a time period to refresh the cache.
2. Apply indexing on all the backend database tables that are used as a source in the report, although your stored procedure is already taking very less time in rendering the data but still applying indexing can further improve the performance at the backend level.
3. Use shared datasets instead of using embedded datasets in the report and apply caching on all these datasets as well.
4. If possible, set the parameters to load default values.
5. Try to reduce the data that is selected by the stored procedure, e.g. if the report contains historical data which is of no use, a filter can be added to exclude that data.
I experienced the same issue. Query ran in SQL just fine but was slow as anything in SSRS. Are you using an SSRS parameter in your dataset? I've found that if you use the report parameter directly in certain queries, there is a huge performance hit.
Instead, if you have a report parameter called #reportParam, in the dataset, simply do the following:
declare #reportParamLocal int
set #reportParamLocal = #reportParam
select * from Table A where A.field = #reportParam
It's a little strange. I don't quite know why it works but it does for me.
One quick thing you may want to look at is whether elements on your report could be slowing down the execution.
For example i have found massive execution time differences when converting between dateTimes. Do any elements on report use the CDate function? If so you may want to consider doing your formatting at the sql level.
Conversions in general can cause a massive slow down so take the time to look into your dataset and see what may be the problem.
This is a bit of a mix of the answers above, but do your best to get the data back from your stored procedure in the simplest and most finished format. I do all my sorting, grouping and filtering up on the server. The server is built for this and I just let reporting services do the pretty display work.
I had the same issue ... it was indeed the rendering time but more specifically, it was because of the SORT being in SSRS. Try moving your sort to the stored procedure and removing any SORT from the SSRS report. On 55K rows, this will improve it dramatically.
Further to #RomanBadiornyi's answer, try adding
OPTION (RECOMPILE)
to the end of your main query in the stored procedure.
This will ensure the query is recompiled for different parameters each time, in case different parameters need a different execution plan.
Related
I have a report which is taking extremely long time to run. It is bringing around 187k rows and it takes around 5 minutes to run. When I checked the execution log table in Reportserver and I noticed that time processing is taking more compared to TimeDataRetrieval and Time Rendering.
Things I did to improve performance:
I made sure that keeptogether property of the report is False so that paging is allowed
The report is not doing any grouping or filtering or sorting. Everything is been taken care at database level.
Caching is not an option for this report, as the report has parameters and they are dynamic values.
Only thing I noticed in the report is for few columns, there are some expressions in the format, which cannot be removed as they are mandatory and was asked by my client. The report has few date columns and I was using following expression:
=IIF(Globals!RenderFormat.Name = "RPL","M/d/yyyy","M/d/yyyy hh:mm tt")
I tried to run the report without the above expression, but I didn't notice any drastic change in performance
I also noticed that TimeProcessing for the report is not constant always. It keeps on changing. How can I make it to constant? Are there any other things I need to change or check to improve performance of the report?
This is basically the same question as "Fast query runs slow in SSRS" however nothing in there I could see worked for me.
Context:
Created a Report Builder dataset to use for my report, query is:
SELECT DISTINCT A.A
, A.B
, A.C
, A.A + ', (' + A.B + '), : ' + CAST(A.C AS VARCHAR) D
FROM Table1 X
INNER JOIN TableA A ON X.Key = A.Key
WHERE (X.Col1 IN (#Param1))
AND (X.Col2 IN (#Param2))
UNION
SELECT '(All)', '(Select to apply all)', 0, '<APPLY ALL>'
ORDER BY C, A
OPTION (OPTIMIZE FOR UNKNOWN)
I have 3 multi valued parameters. The first (#Param1) and second (#Param2) lists load fine and the second is not dependent on the first. The third list which uses the dataset described above is dependent on both 1 and 2 as you can see from the query above.
I add the OPTION (OPTIMIZE FOR UNKNOWN) clause as an attempt to speed it up but to no avail. I do not even know how to declare a multivalue parameter anyhow so this was my only option to try at this stage.
After I am finished selecting values from my second dropdown/parameter and move to the third parameter the report loading icon thing churns for about 5 seconds than it just halts and nothing happens after that and I never get to select from my third dropdown unless I am prepared to wait until it finishes but that would seem to be about 20 minutes, so then after a while I just kill the web-page and start again. When I run the report query in SQL Server in runs in a second and when I run thru the report in the Report Builder IDE it works fine a little delay like seconds as compared to 20 minutes however running via SharePoint/SSRS it takes 20 minutes.
Does anyone have a suggestion to try?
I found my own solution more by accident than ingenious thought and which was purely a mistake on my behalf so sorry to waste anyone's time however it still left me a little perplexed, or perhaps annoyed is a better way to describe it.
Apparently one of my attempts to improve performance also included caching the DataSet which was done a week or so earlier. I had "Cache shared dataset" turned on with a specific daily schedule however no "Cache Refresh Plan" if that makes a difference - probably does as it may have still been using the cached version, i.e. perhaps changing a dataset does not actually force a automatic refresh when loading the data in the drop-down on the report. So in the process of updating my query which was after I had set the caching I went from straight sql to a multi-statement table valued function (with Option optimize for unknown) then to a stored procedure that called my function. So after updating the query in the dataset and refreshing my report that used the dataset because of the cache it was probably not applying my latest change. I turned off the cache and then my report third parameter (Dropdown) started responding. Still quite a bit slow when running in SharePoint where in report builder IDE it is instantaneous however, down to about 10 seconds as opposed to infinite amount of time. So the question I am left with is was using a stored procedure actually effective or was the fact I used the option on the query and further whether to cache or not to cache if it is going to cause a non obvious problem, i.e. will not refresh until the next scheduled period and I am not sure if having a "Cache Refresh Plan" whether it would make any difference. And also more importantly why does running a query via SharePoint as supposed to MS Server Management Studio so much more intricate, I am sure if I wrote my own custom web-page that called the same query it would also be instantaneous - anyhow things to go back to experiment with if I can be bothered.
Obviously data changes overtime and the report similar to another post on this site was working fine then all of sudden it became non-responsive anyhow it is working good enough for now without a need to cache.
I'm working on my first SSRS report and I haven't been able to find general guidelines as to how to create reports. Specifically, I would like to know what the general approach is when aggregate data is needed on a report. For example, let's say I need to show the following in my report:
Pancakes ---34
Eggs----------56
Bacon--------73
I have a several more rows like the above that need to show aggregate data. I'm currently grouping the whole row by type and then on each cell I'm showing a count as follows: [Count(Status)].
My report is already taking 45+ seconds to run. Is it generally preferable to do aggregation like this in the query? Or does this depend on the amount of data being returned? Any pointers are greatly appreciated. Thanks!
As with all SQL answers: it depends.
But generally do your aggregation in SQL. SQL server is much better at performing aggregation than the report layer. Also bringing back less rows will reduce your data transfer and the amount of data which SSRS needs to process. Usually you would only want to do the aggregation at the report layer if there are other constraints which make doing it in the SQL query impossible or if doing so will make the report more difficult to maintain in the future. (There's certainly something to be said for sacrificing a bit of performance in the name of maintainability.) One case would be when you need to display all of the data and returning two datasets is either too complicated or actually slows down the performance of the report.
As a side note, if your report is taking 45+ seconds to run then likely your SQL is not optimized very well or your report is doing a lot of complicated calculations. The more work you can put back on the SQL server the better your performance will be. SQL Server is made for crunching numbers and doing aggregations so certainly let it do what it does best when you can.
YMMV, so always do performance testing for different methods to see what works best.
What is the most efficient way to automate both creation and deployment of simple SSRS reports from one underlying query?
An example query might look like
SELECT Name, ID, Date FROM Errorlog
Query could contain quite a few columns and anywhere from 1 to 1 million rows.
The business purpose behind this question is that I have a sizable number of report queries that need to go out as SSRS reports. I also need the capacity to turn any query I write instantly (or within a matter of seconds) into a simple SSRS report. Unfortunately, doing it through BIDS manually (using toolbox items and creating datasets is cumbersome, slow and unnecessarily repetitive. The only thing I am concerned with is making sure interactive page height/width is zero (to allow scrolling) and that columns are autosized.
How would you accomplish this in a way that is smooth and repeatable?
Let me start by saying that I don't think SSRS will not be very good at this. Specifically on two points this may be troublesome.
First, the number of rows may become a problem. One million results is typically a bit much for reporting services 2008 (though it does depend on the context a bit), it's much better at displaying either aggregated data, or a limited number (up to a few thousand - though again: depending on context) of data rows.
Second, a dynamic number of columns being returned by the SQL side will be a problem. There's only two ways around this that I know of:
Have a denormalized data set with a fixed number of columns, and one or more columns that contain the grouping. Then use a matrix to generate columns dynamically in SSRS. This does have a considerable performance impact.
Generate the RDL dynamically. There's information on the schema to do this, and if you create a good starting point it's very possible. After generating the RDL you'll have to execute it - how to do that depends on your specific setup.
Bottom line is that I wouldn't recommend using SSRS for the task you describe. Consider other technologies that may be better up to this task, e.g. SSIS packages, or perhaps another custom made or third party tool?
If I were you, I'd utilize 'Access Data Projects' which have a wizard for creating report.. that is then easy to upsize to Reporting Services. Right-click IMPORT into a solution full of RDL, and it prompts for MS Access file.
You can easily make a couple of columns into a report using an Access wizard, and then upsize to SSRS.. I've done it hundreds upon hundreds of times like this.
How do I control which stored proc runs first in SSRS. My second stored proc needs to use the temp table data from the first stored proc. Thanks so much.
Dataset Execution Order
http://blogs.msdn.com/b/robertbruckner/archive/2008/08/07/dataset-execution-order.aspx
What you are proposing is a significantly bad idea. If both datasets are sharing a table can you merge them into one result set, then filter or aggregate it in the report.
That said, have you tried reordering the datasets in the RDL (XML) file. I imagine reporting service will run these in order, though it may run them asynchronously. No guarantees.
EDIT:
Adolf's Link confirms it, They do run in parallel unless you set Use Single Trasaction in the datasource. Then they run in the order of the RDL file as I suspected.
If you use a value from the first procedure's dataset to be used to populate an input parameter used by the second procedure, this should ensure that they are called in the desired order.
That said, I agree with jimconstable - it would make more sense to use a single dataset and filter out any unwanted results.