Oh My, How You’ve Grown! Excessive File Size Growth in Management Reporter (MR) Database

Posted by Kraig Kumlin, Sr. Support Analyst on June 13, 2017


Has your MR database gotten so big it’s out of hand?  I recently encountered issues relating to the excessively large size of Management Reporter (MR). So, I wanted to remind everyone of the importance of maintenance of your MR system, and associated data sets.

Here are my recommendations for MR maintenance:

  1. Have a current backup and backup plan in place.
  2. Upgrade your instance of MR.  It will help with disk space, performance, and other issues.  Make sure to backup all saved reports from the reports library.  However, you don’t need to save thousands of reports from six years ago.  Most of this data would be out-of-sync anyways.
  3. Re-inforce and remind users of the importance of file maintenance and file structures.  The MR database contains information on all users in MR, their security, and a full range of settings.  Reports generated are also stored in the reports library, which is also contained in the database.
  4. Remove users no longer with your organization.
  5. Have a schedule in place to remove old reports or archive them to a second location.  We have seen many performance and connection issues happen due to this lack of maintenance because the database size grows too big.

 

If you would like to go over your maintenance schedule, set up a new plan, or need assistance with your MR system, send out team of experts an email at Support@Crestwood.com.


Share this:
 
 

Comments:

Add your comment: