Thursday, June 19, 2014
Removing the Old Data Mart in Dynamics GP Management Reporter
Posted by Greg Horner
Recently we had a few customers with a heavy load of financial data in GP, which can gum up the refresh process. Here are two tips to help to overcome these data mart challenges in Dynamics GP Management Reporter 2012:
- Sometimes, when attempting to refresh the data mart, you think the data mart is removed, but it isn’t.
Scenario: You first disable the data mart, then proceed to remove it in the configuration console. After you do that, you remove the data mart in the SQL database. When trying to rebuild the new data mart, you get an error saying that the “integration is already in place.” This is because the data mart never was completely removed.
Solution: To fix this, you can create a blank database in SQL called “ManagementReporterDM” and then remove the data mart one more time from the configuration console.
- If you have difficulties refreshing a data mart, error logs are created. These can get quite large if you are not checking on things. (You can setup a notification, but that’s another discussion.)
These messages are stored in a table in Management Reporter called “scheduling.Message.” You can see how many records are in this table by running a select statement. Select * from scheduling. Message or select count (*) from scheduling.Message to get a count of those messages.
We had a customer with a count in the millions, and that was slowing down the process of removing the data mart. We simply ran a select statement (truncate table scheduling.Message) to remove those records, which allowed us to successfully remove the data mart.
If you need further assistance and support with Dynamics GP, please don’t hesitate to contact us (help@armaninoLLP.com).
Greg has over 20 years of accounting experience and specializes in training and implementing. Greg’s key areas of expertise are Core Financials, Management Reporter 2012, Payroll, and Report Writer.