Saturday, 2 April 2016

Mirth Connect using SQL Server

When you first install Mirth Connect is comes with its own Derby database.  This is fine when you are mucking around and developing channels, but I have seen my fair share of production sites going down because Derby is not up to task.  After a bit of research I even found Mirth themselves recommend that you replace this database before going live.

The first thing I do with Mirth now on a fresh install is to configure it to point to SQL Server.

Fortunately this is pretty easy to do.
Load up Mirth Connect Server Manager, then navigate to it in your task bar.

Right click it, and select "Show Manager"

Navigate across to the "Database" tab and fill it out with the settings and connection string to your SQL Server.

One thing to watch for is if your SQL is not the default instance you can't just use the normal / syntax of specifying it along with the server name. Use the following instead:

Now just restart the Mirth service from the Server Manager and Mirth will build and prepare the database for you.

If you need to migrate an existing database, and keep all the data then I suggest you take a look at this link I found.


  1. Really appreciate all the stuff made by this blog to let people know more about this topic. I added little more relevant points to my knowledge which definitely going to help me in coming future.
    vSan 6 Standard for 1 processor

  2. Thanks. You solved my connection issue when I tried to move to sqlexpress.

  3. for me it is not working on port 1433

  4. Thanks very much for this! Our DB instance is not the default instance on the server, so this was super helpful.