# Tag Historian & MySQL Archive Engine

**URL:** <https://forum.inductiveautomation.com/t/tag-historian-mysql-archive-engine/11640>\
**Category:** Ignition\
**Created:** [May 10, 2016, 4:39pm UTC](https://forum.inductiveautomation.com/t/tag-historian-mysql-archive-engine/11640 "2016-05-10T16:39:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![simon.avantecnia](https://avatars.discourse-cdn.com/v4/letter/s/9de053/32.png) [@simon.avantecnia](https://forum.inductiveautomation.com/u/simon.avantecnia)\
**Post date:** [May 10, 2016, 4:39pm UTC](https://forum.inductiveautomation.com/t/tag-historian-mysql-archive-engine/11640/1 "2016-05-10T16:39:02Z")

</div>

Does anybody know if the Tag Historian feature/module is compatible with the “ARCHIVE” MySQL Engine? Maybe with some tweaking?  
I was hoping that I could shrink my database size…  
Disclaimer: I’ve tried but it doesn’t seem to like it.

---

<div class="post-metadata">

**Author:** ![unyogac](https://avatars.discourse-cdn.com/v4/letter/u/8e8cbc/32.png) [@unyogac](https://forum.inductiveautomation.com/u/unyogac)\
**Post date:** [July 28, 2016, 2:04pm UTC](https://forum.inductiveautomation.com/t/tag-historian-mysql-archive-engine/11640/2 "2016-07-28T14:04:24Z")

</div>

I have a similar question. I am planning out a new system and would like to archive any data older than 3 months. If I set up the historian to partition by month on a mysql database, it looks like I’ll get tables named sqlt\_data\_#_####_##.

Can I convert these tables (for months older than 3) to use the archive engine instead of the default innodb without messing up ignitions ability to read the data from the remaining innodb tables (data 3 months and newer)?

Can ignition read the archived data as is (as historian tags)?