Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested answer

How to handle when your AXDB transaction log is much bigger than AXDB it self ?

(0) ShareShare
ReportReport
Posted on by 522

Hi guys,

I'm beginner in Dynamics D365 especially when working inside VM using Hyper-V. Also I have very limited knowledge about SQL administration.

Question is what can we do when the transaction log of AXDB is much bigger than AXDB it self ?

I'm running out of space inside my VM which I no longer can expand the VM disk since my laptop space also small.

The current condition if I take a look at the DB size is : 

AXDB is only 3GB, but the transaction log is 71GB.

pastedimage1684599484510v1.png

While this is "just" a log, can I just delete this ? does it create new Log file ? can this corrupt my D365 FO ?

As far as I know, the log will be truncate when I'm doing Backup -> Transaction Log from SSMS, but since my VM space left is less then 70GB (only 30GB), it will show error no available space. I assumed it need to at least 70GB available space as well  for the backup ?

Any idea how to handle this ?

Thanks

  • Ken Manhattan Profile Picture
    522 on at
    RE: How to handle when your AXDB transaction log is much bigger than AXDB it self ?

    Hi Andre, unfortunately no. Is deleting log you are referring is the effect when we change the recovery model, or you are referring to the "manual" work of delete the physical file like my question in the 1st place ?

    Btw, the advice from Mohit is working perfectly. And it is my DevBox so I think should be no problem to just change the recovery model to simple. Now I have more space.

    Thanks both.

  • André Arnaud de Calavon Profile Picture
    293,245 Super User 2025 Season 1 on at
    RE: How to handle when your AXDB transaction log is much bigger than AXDB it self ?

    Hi Ken,

    In addition to the reply from Mohit. Are you able to attach another disk to the VM? Then you can create the backup on the other disk. Just deleting the log is dangerous. You must create the backup for shrinking the log files after you change the recovery model to simple anyway.

  • Suggested answer
    Mohit Rampal Profile Picture
    12,556 Moderator on at
    RE: How to handle when your AXDB transaction log is much bigger than AXDB it self ?

    Hi Ken, Instead of deleting the Transactional log DB can you try changing recovery mode to simple.

    Check this article

    dallasdbas.com/.../

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

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 293,245 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,925 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156 Moderator

Leaderboard

Product updates

Dynamics 365 release plans