Announcement

Collapse
No announcement yet.

Message pruning in Mirth (3.5.1)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Message pruning in Mirth (3.5.1)

    Hi All,

    I have set pruning in settings for 1 day (as there is too much of data in a day).
    Schedule to run the pruner is set for 1 AM.

    I need to understand what happens when pruner runs in little detail.

    I have below understanding of pruner theoretically
    It deletes all saved messages in channel as per the "prune data older than settings" set inside channels.

    Practically when i run it:-

    It does not reduce the size of Mirth DB immediately, In fact it increases it slightly. Why database is not reduced as soon as the pruning runs ?

    Regards,
    Dev

  • #2
    Hello,


    datapruner does not release the space in the DB, to do that after the pruning you need to perform/run "Vacuum" (Postgres) or "Shrink" (SQL Server) in Oracle i don't know.
    Best Regards,
    Alex Neiva

    Comment


    • #3
      what!!!!!

      wooo...thanks a lot for the input, that was a news for me.
      But why cant Mirth itself do a vacuum/shrink right after it prunes ?


      Regards,
      Dev

      Comment


      • #4
        Hello,


        i don't really know why but i know that because i saw that in the forum one time.
        That is why Mirth advice to set autovacuum ON in server productions:
        http://www.mirthcorp.com/community/w...production+use


        I guess this a DB "thing" and can not be considered a "issue/problem" in Mirth... from my point of view i thing this is DB management.
        Best Regards,
        Alex Neiva

        Comment


        • #5
          It's normally bad practice to shrink a db if it is expected to grow right back to where it was before you shrunk it. The database will reuse the space within the file that was freed before it makes the file larger.

          Comment

          Working...
          X