SSRS Report Preview Problem

Hi,

I have created a dashboard report that connects to several different database connections. The report takes several minutes to run due to the amount of data that is being queried.

I have just tired to preview the report and I am getting the following error:

SSRS Preview Error
Please could someone help? Is this a time-out issue?
spen_langAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

prequel_serverCommented:
so it successfully runs sometimes and shows this error at other times?
0
spen_langAuthor Commented:
Yes, I believe it is a time-out issue in Visual Studio 2008. The dataset is very large and therefore takes several minutes to load the report. I reduce the parameter range, reducing the dataset size the report runs fine.

There is no problem running the report in production once it has been uploaded to the report server.

I think I will have to put this down to another Microsoft bug...
0
prequel_serverCommented:
not really a bug but yes it's possible to get different behavior in Visual Studio vs running the report in the report server.  When the report is deployed onto the report server it has more resources to fetch and compile data than the Visual Studio client.  Having said that, how long does this report take in your production report server? Several minutes is not acceptable in today's inpatient society so I'm wondering how your users/the person consuming this report feels about the length of time it takes to render.

There are several ways to make it run faster. One way is to use SSIS to setup a few ETL jobs that would get the data for the report preemptively and stores it on a local sql server db.  The data would be pre-compiled and pre-aggregated to a level that's granular enough for the user. Then when the user run the report, the data is fetched from one data source and gets less rows so it will run much faster.  If you can't do this warehouse model that you may want to look at optimizing your query for better performance.

cheers
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
spen_langAuthor Commented:
Hi,

Thanks for your recommendations, I would like to do this but I just haven't got the time to do this.... The report is a KPI dashboard report that compares year on year data, so the dataset is always going to be very large. The report is Snapshot every 12 hours so the users do not notice the slowness of the running of the report.

Thanks, Greg
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Development

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.