Backing up the NAV SQL Transaction Log

A._B._Computer_SystemsA._B._Computer_Systems Member Posts: 103
Have a NAV 4.0 SQL customer who did not back up their SQL Transaction Log for a long time. Now it is very big and when they try to back it up so all completed transactions are removed, there is not enough disk space to do so. Any ideas how to recolve that without taking any risks? Seems like it got very big very fast because they by mistake activated NAV Change Log for all fields.

Comments

  • ara3nara3n Member Posts: 9,255
    delete all the entries in the change log table. Do a navision backup. Rename the database on sql to something like olddb.
    Create a new db and restore the navision backup .fbk.

    And you should be set with small transaction log, and a small db.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • bbrownbbrown Member Posts: 3,268
    Do the backup to a device with enough space.
    There are no bugs - only undocumented features.
  • DenSterDenSter Member Posts: 8,304
    Create a full backup first, then truncate the transaction log. Disable the change log next, and you're al lset. You may want to shrink the transaction log file (use DBCC SHRINKFILE, and specify the file size you want, and leave enough space to accommodate for the transaction log). Then you set up a proper backup strategy.

    Send me a PM if you need help setting that up.
  • ajhvdbajhvdb Member Posts: 672
    bbrown wrote:
    Do the backup to a device with enough space.

    Yes, just keep providing the extra backup tapes (and reuse them while backup up).
  • kinekine Member Posts: 12,562
    Yes, transaction logs cannot be backed up if there is no free space on the disc. But you can still do full backup as others suggested and cut the logs.
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
Sign In or Register to comment.