# Database Redundancy

**URL:** <https://forum.inductiveautomation.com/t/database-redundancy/7641>\
**Category:** Ignition\
**Created:** [November 29, 2013, 2:27pm UTC](https://forum.inductiveautomation.com/t/database-redundancy/7641 "2013-11-29T14:27:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![george](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/george/32/14066_2.png) [@george](https://forum.inductiveautomation.com/u/george)\
**Post date:** [November 29, 2013, 2:27pm UTC](https://forum.inductiveautomation.com/t/database-redundancy/7641/1 "2013-11-29T14:27:01Z")

</div>

I’d be interested to know how people have handled redundancy with respect to a database (specifically MS SQL Server).

We’re looking at a project where the customer has asked for “fully redundant servers so no data is lost”.

Now obviously there is a redundancy option for Ignition itself but what that doesn’t really cover is what to do in terms of the database.

As well as SQLtag history I could quite feasibly have transaction groups plus inserts/updates/deletes and stored procedures within scripting as well.

What’s the best way to cope with the database failing?

---

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [November 30, 2013, 3:49pm UTC](https://forum.inductiveautomation.com/t/database-redundancy/7641/2 "2013-11-30T15:49:55Z")

</div>

database replication is outside of Ignition. I have tried using MySQL replication, but it is flaky at best and needs constant babysitting. Sort of hard to do when you set up an application in a remote plant with no IT support.  
I believe MS SQL Server may be more robust in replication, but I have not tried it yet.