Management Reporter Initial Build taking too long

(0) Share

Report

Posted on by Sunil Chhabra

1,930

I have a new server - installed GP - upgraded all the databases successfully

Installed fresh copy of Management Reporter and configured the datamart. The initial build is taking very long - I started the process about 12 hours ago.

I have 4 databases and it states the databases are ready at the bottom of the MR Configuration window.

All GP databases are configured to enable General Ledger reporting in Company Options as we are using MR on a separate server 2016. Once the MR installed is completed I will then import the reports.

Thanks

Categories:

Microsoft Dynamics GP

All responses (4)

Answers (1)

Suggested answer

Beat Bucher GP Gee... 28,021 Super User 2024 Season 1 on at

Like (0)

Report

RE: Management Reporter Initial Build taking too long

I'd start by making sure the historical companies are not setup in the MR 2012 configuration console and are disabled for reporting in the GP Company preferences.

There is no point in having the DM grab data from GP companies you're never going to report against..

With only 1 company to report against to, I'd get rid of the DataMart and use the Legacy connector, as it is much more reliable and you'll never have to refresh anything, not to speak about the disk space you're going to recover from the deleted MR DataMart database...
Sunil Chhabra 1,930 on at

Like (0)

Report

RE: Management Reporter Initial Build taking too long

Thanks - I have 4 companies - 3 are historical. You are correct we only run reports from 1 company but the datamart is built for all 4 companies.
Suggested answer

Beat Bucher GP Gee... 28,021 Super User 2024 Season 1 on at

Like (1)

Report

RE: Management Reporter Initial Build taking too long

Hi,

Let's start with the basics...

How many companies do you have to report against ?

How many years of historical data do you have in all of those companies ?

The DataMart is the least efficient way IMHO to get financial reporting out of GP.. Truth is if you have dozens of GP companies and Years of historical GL data to report, then DM is not the way you want to go, as it will just create a huge DM database for data you're unlikely to ever report for.. Who reports against data that is 10+ years old ??? no one, but that exactly what the MR DM does, because it has no ways to limit the number of years you want to report against. It just sucks all the GL data (current & history) from your GP companies and piles them into a big database..

I recommend to all my customers to stick with the Legacy connector in GP as you'll never run into those sort of problems nor face any data integrity problems due to changes to your Chart of Account in GP.
Verified answer

Greg Byer 2,586 on at

Like (1)

Report

RE: Management Reporter Initial Build taking too long

Click on Logs | Data Mart Integration, on the left side of the MR Configuration Console window. Then click the Refresh button and see if there are any error on any of the integrations.

You'll also want to check how much memory is installed on the MR server and SQL Server. MR does require a good amount of memory. For a small database (50 million GL transactions or less), MR requires:

4 GB for the MR Application service

16 GB for the MR Process service

32 GB for SQL Server

If you have MR install on your SQL Server, you'd need at least 52 GB RAM just for MR. Less than that and you'll see performance issues with the integration and processing reports.