Announcement

Collapse
No announcement yet.

1.8 to 2.1 upgrade with Derby to SQL/PosgreSQL

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

  • 1.8 to 2.1 upgrade with Derby to SQL/PosgreSQL

    I'm looking to upgrade our production server from 1.8 to 2.0 (or 2.1) to take advantage of the feature that allows individual channels to be deployed/undeployed and the performance tweaks. We have roughly 30 channels running on this machine that are various combinations of file readers and HL7 interfaces. We are fortunate that we can afford some down time to accomplish this. While we're doing this, we thought it would be a good idea to move off the Derby engine and onto either MS SQL or PostgreSQL back end.

    We already have a MS SQL Server on another machine with resources to spare, but we thought about installing PostgreSQL on the Mirth Server and going that route. The theory behind this was to keep everything for Mirth on one box. Are there any clear advantages to one direction over the other?
    Any advice anyone can give?

  • #2
    I'd pick PostgreSQL to keep it on the same box (no network latency). In addition to that, PostgreSQL is the most tested database for Mirth Connect.
    Jacob Brauer
    Director, Software Development
    NextGen Healthcare

    sigpic

    Comment


    • #3
      To make the migration easier, you could export your server configuration from the 1.8 system (under the Settings panel) and import it into your 2.0 system. This should import all of your channels and run any conversion needed between the two versions. As always, make sure to create a backup of your mirthdb folder before making any changes.
      Gerald Bortis | Chief Information Officer | Mirth Corporation

      Comment

      Working...
      X