You’re offline. This is a read only version of the page.
5,901
Dear All,
Can you please let me know what are the best approach to create complex SSRS report.
Means no performance issue, no timed out etc. Smoothly run report by end user.
Please give me more shed on this.
Thanks!
Arpan
*This post is locked for comments
Please kindly mark the answers which you have found to be helpful with the checkbox next to each post, in order to resolve the thread and assist others.
He talked about raw data for the entire table. You could check size per DB or per table with the sp_spaceused stored procedure in SSMS.
You are asking what you already have answer for. Follow the links I provided, they have plenty of explanation on what takes long and what to avoid/overcome with which techniques.
my suggestion in huge data and complex data sources In addition to Vilmos Kintera reply, try to decrease joins and links, create multiple reports instead of one report that includes everything
ex. our customer needs one report for sales and collection with customer details and sales analysis and his database size above 500 GB, after design, this report performance is very bad.
we divide this report to 3 reports (one for customer details with statistical data like one for collection, and other for sales analysis )
this is a real case with us,
so based on your case you will provide the best practice for this case
Thank Vilomos,
As said "Sorting, grouping, counting and adding a lot of joins are generally all performance killers,". Suppose as per my requirements i need this all (Sorting, Grouping, multiple joins) but how to avoid this all?
please give me more shed on this.
Thanks!
Arpan
[View:https://msdn.microsoft.com/en-us/library/dn251070.aspx:750:50]
Series of performance articles on SSRS reports by Microsoft Perf Team:
[View:https://blogs.msdn.microsoft.com/axperf/tag/ssrs/:750:50]
[View:https://blogs.msdn.microsoft.com/axsupport/2013/09/18/microsoft-dynamics-ax-2012-reporting-tips-how-to-improve-performance/:750:50]
Make sure you do not return full table buffers but only the fields you actually need. Sorting, grouping, counting and adding a lot of joins are generally all performance killers, keep it simple. Also make sure your selection criteria has covering indexes on the tables.
Finally, no reports will run fast if you do not do regular SQL database maintenance and health checkups.
https://www.daxrunbase.com/2016/05/11/ax-database-tuning-and-maintenance/
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (