April 15, 2020 at 1:29 pm
We use SSRS on SQL Server 2016 and on it have a skype usage report run. This report is completly third party and was installed along with skype.
All other reports seem to work fine but on this one report, when running the report loading screen sits there for a long time without the report ever showing. But the strange thing about it is that it seems to run fine with any other value apart from one and this one is what I need to produce a report on.
Im not sure where to look to fix it so that it will work for this one value, I will be unlikely able to change the codeing of the sql calls in the report or any underlying stored proc as its a third party product and we are generally not allowed to do such things.
April 16, 2020 at 2:10 pm
Thanks for posting your issue and hopefully someone will answer soon.
This is an automated bump to increase visibility of your question.
April 16, 2020 at 6:23 pm
If it runs fine for other parameters but not for this one, it might be a bad parameter sniffing issue. The stored proc is third party so you can't modify it, but are you able to recompile it? If so, maybe try that and then run it for your problematic parameter (don't run one of the others first). This is just a guess, though.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply