Breaking news from around the world
Get the Bing + MSN extension
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
In our production, suddenly reports become very slow. We have checked the following things.
1. Executionlog in report server. The report queries are executed within 100 to 200ms.
2. We checked SQL server CPU and Memory utilisation. CPU was normal but memory was around 95% and it is consumed by SQL server service. It is same during the report run. We reset the iis. The memory consumption reduced to 7%. Report was rendered little better than earlier. But still we couldn't get back to the old performance level which was quick.
Is there anything else should be checked? Please suggest.
D365 220.127.116.11 on premise.
SQL server 2016
Thanks in advance.
If you do not limit SQL RAM consumption, it consumes almost all of the RAM, so 95% is normal.
Have you changed your security model recently?
Have youtried to execute SQL script of report directly to SQL? May be you need to rewrite some points there for optimization.
Thanks for the suggestion. Yes, we even executed the query directly in SQL. It is very fast. I don't think issue is with the query. Because even simple report created using report wizard is also very slow.
We tried executing the reports directly from the report server url. Reports rendered very quick.
The SQL RAM usage could be the problem, as RAM would need to be freed up to load Reporting Services and/or the SSRS connector, and that time would not be shown in the RS execution log. I'd suggest restricting the SQL RAM so that the server is running at maybe 85% RAM, and see if that makes a difference
Thanks for the response.
We did reset the iis which reduced the memory consumption to 7%. After the reset, there is an improvement in the performance but still it is not like the past.
Business Applications communities