# How to store longer json strings in tag history?

**URL:** <https://forum.inductiveautomation.com/t/how-to-store-longer-json-strings-in-tag-history/56324>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [February 18, 2022, 7:54pm UTC](https://forum.inductiveautomation.com/t/how-to-store-longer-json-strings-in-tag-history/56324 "2022-02-18T19:54:11Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![josborn](https://avatars.discourse-cdn.com/v4/letter/j/4bbf92/32.png) [@josborn](https://forum.inductiveautomation.com/u/josborn)\
**Post date:** [February 18, 2022, 8:22pm UTC](https://forum.inductiveautomation.com/t/how-to-store-longer-json-strings-in-tag-history/56324/2 "2022-02-18T20:22:47Z")

</div>

The historian uses VARCHAR(255), or the equivalent of your flavor of SQL. You could try changing that, but its probably not a good idea, especially not if you have partitioning enabled. You could write your data to a table of your own design with scripting.

This thread has some good info that may help:  
([Storing Datasets in MySQL Blobs](https://forum.inductiveautomation.com/t/storing-datasets-in-mysql-blobs/19905))

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-to-store-longer-json-strings-in-tag-history/56324)._