web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / MR Log file is tremend...
Microsoft Dynamics GP (Archived)

MR Log file is tremendously large

(1) ShareShare
ReportReport
Posted on by Richard Wheeler 75,848 Moderator

We have an MR database that is about 400MB in size. The log file has now topped 80GB. The recovery model is set to simple and nightly backups are performed. I am thinking of changing the recover model to full and to perform transaction log backups to keep the log file small. When MR runs and generates reports are these older versions of the reports being kept in the log file? What makes the MR log file grow so large and so rapidly?

*This post is locked for comments

I have the same question (0)
  • kdraper Profile Picture
    kdraper on at

    I had the same problem.  I deleted hundreds maybe thousands of historic reports then I shrank the log.  It has been fine ever since.  

    roseasp.com/my-what-a-big-management-reporter-log-file-you-have

  • Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,058 Moderator on at

    Hi Richard,

    This is very strange... in Simple recovery mode there shouldn't be any log written by SQL.. the LDF file should not grow at all... What I do in such cases is detach the database (stop the services before), rename the LDF file and then re-attach the DB.. SQL automatically creates a new default LDF file of 512kb... once done, delete the 80GB LDF file..

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at

    I usually prefer not to shrink the log file but sometimes I see things like this that leaves no choice. From there I would watch the log file and hopefully I see one day where it grows very rapidly. Then I ask what people were doing the day before. Now if the log files slowly grows that presents a bigger challenge. I know in GP running check links will make the log file grow or if a large insert or delete is performed but for MR to behave this way is strange.

  • Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,058 Moderator on at

    I agree Richard,

    But the point is that you said the recovery mode is set to 'Simple' ... thus the log file shouldn't grow at all, not even when doing clean-up actions like Kerry mentioned ...

    This sounds fishy to me... try to switch the recovery mode to Full and then back to Simple. Do a full backup and then try what I suggested previously (detach/attach) . Then keep an eye on the log file...

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at

    The log files grow even under simple recovery model because they are set to auto grow. That could be turned off but the point here is to find out what is making it grow. My suspicion is this client runs reports and keeps every single version.

  • Suggested answer
    Beat Bucher GP Geek GPUG All Star Profile Picture
    Beat Bucher GP Gee... 28,058 Moderator on at

    Have a look at this SQL thread about Log files and growth..

    dba.stackexchange.com/.../why-does-transaction-log-continue-to-grow-in-simple-recovery-mode-with-nightly-b

    I agree that this shouldn't happen, but the reality is that in Simple recovery mode, SQL continues to log transactions without ever cleaning the log file until you issue a DBCC shrink.

    I usually take on my production system a 15-min log backup cycle to keep the logs small and do a full backup nightly.. still some log files keep growing pretty large for no reason and yes I suspect MR is one of those apps that writes a lot of records in the DB for nothing... MS should come up with an option to self-clean the reports after a certain period of time, because the MDF file keeps just growing too with all the version that are added to a report library.

    I run also a weekly re-index on the databases to keep the data access efficient.

    I must confess that this is the weak side of the Dynamics GP documentation, as there is nothing mentioned about your data maintenance as MS thinks that every GP admin is de-facto a full DB Admin as well :-)

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at

    For the vast majority of our clients the log files either do not grow or grow very slowly. Doing an upgrade or check links will often force the log file to grow. This issue with MR is an exception to the rule. To have a 500MB data file and an 80GB log file is highly unusual. Is this case we simply advised their IT staff what was occurring so they could plan accordingly. We did ask the users to purge all those old reports which I am sure has never been done.

  • Richard Wheeler Profile Picture
    Richard Wheeler 75,848 Moderator on at

    Also, a simple shrink of the log file will force it to shrink. Simple recovery does not stop the log file from growing. For our clients who do not have the staff or resources to plan for a point-in-time recovery the recovery model is set to simple. We try to explain the reason why not to do that but the customer is always right.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans