70
We have a couple of reports that can run in a couple of minutes and then balloon to a half an hour. Any tips out there on how to speed up the reports? The Database ManagementReporterDM is 157 Gif....SQL server is 32 Gig. Any Recommendations on index tuning????
Hi Patrick,
The system requirements are based on the number of records in the GL (GL20000 and GL30000 tables) for all companies that integrate into MR. If you had 112 million records in your GL, that would be considered a large database and would need 128 GB RAM for SQL Server and 32 GB RAM for the MR process service.
Greg, thanks for your response. We have 112 Million rows in our fact tables. Is that what the document referring to?
Large database • Between 100 million and 200 million transaction lines • 128 GB RAM for SQL Server
• 32 GB RAM for the process service
I do not see memory pressure on the application server but I definitely see memory and CPU pressure when a report is invoked.
If you can answer the question that we have a large Management Reporter DB, that will help in the justification for more memory on the sql server. We currently have 32 Gig.
Thanks again,
Patrick
There are a number of things that can influence the time it takes to generate a report. Things like the detail level (Financial; Financial & Account; Financial, Account & Transaction), if unposted activity is included, if a reporting tree is included, calculations, YTD columns--as you get later in the year, YTD columns gather more data. All of these will add to the time it takes to generate a report. You can try running sp_updatestats on your ManagementReporter database. You'll also want to make sure that you have the recommended amount of memory installed according to your database size. System requirements can be downloaded here: www.microsoft.com/.../details.aspx
Share
Report
All responses (
Answers (
