web stats
MS SQL Express db hitting max size - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #1  
Old 02-11-2020, 01:33 PM
johnlhall johnlhall is offline
Mirth Newb
 
Join Date: Nov 2016
Posts: 7
johnlhall is on a distinguished road
Unhappy MS SQL Express db hitting max size

Initially when we installed Mirth we set it up with MS SQL Express for the DB as we are primarily a MS SQL based practice. This setup was great for the first three years however recently we added an immunization interface and even with pruning daily the db hits 10gb and stops accepting messages.

At this point it is clear we need to migrate to a different db server whether that is MariaDB or MYSql I don't know or care as long as the tools are there. I would have loved to just move the db off the Mirth server to one of the bigger DB Servers but the express is 2016 and all the other DB servers are 2012 hence we can't even just move the db to a different server.

I have hunted around for a recent guide but have been unable to find out and nothing for migrating from SQL to something else.

If someone can point me in the correct direction that would be great.
Reply With Quote
  #2  
Old 02-12-2020, 10:21 AM
hugito24 hugito24 is offline
Mirth Newb
 
Join Date: Feb 2020
Posts: 7
hugito24 is on a distinguished road
Default

Hi there,

I was wondering if you couldnt just configure a new DB (putting all the table and data you already have), for example MySQL, that has way more space available than 10GB.

And Then just point Mirth to that new DB, and do the changes you need on the channels.
Reply With Quote
  #3  
Old 02-12-2020, 10:25 AM
johnlhall johnlhall is offline
Mirth Newb
 
Join Date: Nov 2016
Posts: 7
johnlhall is on a distinguished road
Default

Since I am clearing the db daily I think that would be fine. Is there a set of instructions for this as I do not want to recreate the channels again and load the certificate required for our main channel?
Reply With Quote
  #4  
Old 02-12-2020, 10:35 AM
ricber ricber is offline
Mirth Guru
 
Join Date: Jun 2007
Location: Barcelona, Spain
Posts: 185
ricber
Default

HI johnlhall,

I was wondering 10 Gb each day just adding inmunizations? I don't know what requirements you have but, do you really need all this amount of information?. It sounds like you are storing base64 content in your database that you really don't need, am I wrong?.

Maybe adjusting loggin level in your channels let you work with same database. If I'm really wrong, take a look at Postgres.

Hope this helps,

RB
Reply With Quote
  #5  
Old 02-12-2020, 10:36 AM
dforesman dforesman is offline
Mirth Newb
 
Join Date: Mar 2016
Posts: 25
dforesman is on a distinguished road
Default

Did you change the channel message storage to something like Raw?

Otherwise what I have experienced in the past is taking the Mirth service offline, backing the Mirth DB up, make backups of all your channels (just because), restoring the DB to different server then pointing Mirth to that new DB server/instance, bring mirth back online, celebrate with drinks.

Worse case scenario is you point it back to the original and regroup.
Reply With Quote
  #6  
Old 02-12-2020, 10:45 AM
johnlhall johnlhall is offline
Mirth Newb
 
Join Date: Nov 2016
Posts: 7
johnlhall is on a distinguished road
Default

I have already set the logging to error level. The issue is the number of responses we receive from the registry. Any single patient will result in ~50 messages from the registry. We have 80 providers, 9 clinics so we schedule a lot of patients per day and the systems asks for the imms data every time (unfortunately we can not configure this)
Reply With Quote
  #7  
Old 02-12-2020, 10:46 AM
johnlhall johnlhall is offline
Mirth Newb
 
Join Date: Nov 2016
Posts: 7
johnlhall is on a distinguished road
Default

Message storage is set to Production
Reply With Quote
  #8  
Old 02-12-2020, 10:48 AM
johnlhall johnlhall is offline
Mirth Newb
 
Join Date: Nov 2016
Posts: 7
johnlhall is on a distinguished road
Default

As for restoring to a different server the issue is that the current express server is 2016 and we do not have a database server with anything higher than 2012R2 and you can't restore a database to a lower level server than the one it was backed up on.
Reply With Quote
  #9  
Old 02-12-2020, 10:51 AM
dforesman dforesman is offline
Mirth Newb
 
Join Date: Mar 2016
Posts: 25
dforesman is on a distinguished road
Default

Then the MSSQLDB backup/restore may be your best option at this point.

Or a job that runs and deletes the messages out of Mirth every X mins, but that could cause performance issues.
Reply With Quote
  #10  
Old 02-12-2020, 11:20 AM
johnlhall johnlhall is offline
Mirth Newb
 
Join Date: Nov 2016
Posts: 7
johnlhall is on a distinguished road
Default

Quote:
Originally Posted by dforesman View Post
Then the MSSQLDB backup/restore may be your best option at this point.

Or a job that runs and deletes the messages out of Mirth every X mins, but that could cause performance issues.

Backup and restore was unsuccessful as the source is on a higher version of SQL Server than the destination.
Reply With Quote
Reply

Tags
database maintenance, migration;sql

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -8. The time now is 02:54 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
Mirth Corporation