Announcement

Collapse
No announcement yet.

That is stored in the database?

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

  • That is stored in the database?

    Hello,

    Would like to know which is stored in the BD. Messages waiting?

    Thanks.

  • #2
    The Mirth database stores channel configuration data, channel statistics, as well as message data in all stages of processing (raw, transformed, and sent) along with some metadata (date received, sender, protocol, etc.). Note that messages will not be stored if the "Store message data" option is not selected on each channel's summary page.
    Gerald Bortis | Chief Information Officer | Mirth Corporation

    Comment


    • #3
      Originally posted by geraldb View Post
      The Mirth database stores channel configuration data, channel statistics, as well as message data in all stages of processing (raw, transformed, and sent) along with some metadata (date received, sender, protocol, etc.). Note that messages will not be stored if the "Store message data" option is not selected on each channel's summary page.
      We wanted to keep messages for logging purposes, but some of our larger payloads were causing quite a bit of disk space to be eaten up. A sent message will generate both transformed and sent message records, each with three payload fields. In many cases a payload ends up being duplicated at least once across those records, with an increasing frequency of this as you start cascading messages through channel-writer/reader parent/child channels.

      As a workaround to this we have done some trigger and fisheye configuration tweaking to pull an md5 checksum on the message payload, store the payload in a seperate table keyed by the hash value, and then push the hash in the payload's place in the message record to serve as a pointer back to the payload table for dereferencing on queries to the message table. While the threat of hash collision is there, we figure the frequency of such a collision and the minor performance hit of splitting the payload out like this are both acceptable when considering the gain in disk efficiency while also being able to store off a more verbose log/history.

      As an added step, we've also taken to partitioning off the message table by both status and date created to allow us to shift the load across multiple table spaces and be able to quickly truncate out messages of a given type after a certain period to balance some of the load of the autopruner.

      Comment


      • #4
        Ran into the same problem at a previous employer.

        We solved it by having our 'primary' Mirth instance prune its messages once a day. That instance would insert a copy of each raw message into a separate 'logging' database.

        This kept the Mirth database nice and thin, and ensured that access to the logging database for reports or analysis didn't bog down live messages.
        Jon Bartels

        Zen is hiring!!!!
        http://consultzen.com/careers/
        Talented healthcare IT professionals wanted. Engineers to sales to management.
        Good benefits, great working environment, genuinely interesting work.

        Comment


        • #5
          Originally posted by geraldb View Post
          The Mirth database stores channel configuration data, channel statistics, as well as message data in all stages of processing (raw, transformed, and sent) along with some metadata (date received, sender, protocol, etc.). Note that messages will not be stored if the "Store message data" option is not selected on each channel's summary page.
          I would like to know where is the channel configuration data stored in the Mirth Connect folder. I am working on version 3.6.0 and it has crashed which has left me with no access to my channels. Is it possible to do a re-install of some of another version and copy data from existing folders?

          Comment


          • #6
            I upgraded to Mirth 3.6.1 and all my data is intact.

            Comment

            Working...
            X