# Turn on History on a Dataset

**URL:** <https://forum.inductiveautomation.com/t/turn-on-history-on-a-dataset/16944>\
**Category:** Ignition\
**Created:** [February 9, 2018, 7:55pm UTC](https://forum.inductiveautomation.com/t/turn-on-history-on-a-dataset/16944 "2018-02-09T19:55:20Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![R.Alamsha](https://avatars.discourse-cdn.com/v4/letter/r/e5b9ba/32.png) [@R.Alamsha](https://forum.inductiveautomation.com/u/R.Alamsha)\
**Post date:** [June 29, 2018, 9:56am UTC](https://forum.inductiveautomation.com/t/turn-on-history-on-a-dataset/16944/11 "2018-06-29T09:56:12Z")

</div>

> [@abhimanyu.chopra](#):
>
> Is there anyway history can be enabled for datasets, or is there a better method to do this?

If you don't have a reliable MQTT driver for Ignition, i would recommend this solution:

1. Log MQTT payload to a database.
2. Consume it with query tags into Ignition.

[![](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/c/1ca98c6b552444c535272dc4c140c2704b6be2d3.jpeg "Learn, How to save MQTT messages into a MySQL Database") ](https://www.youtube.com/watch?v=Tp5EFG4W5WU)

[https://www.raviyp.com/embedded/233-learn-how-to-save-mqtt-messages-into-a-mysql-database](https://www.raviyp.com/embedded/233-learn-how-to-save-mqtt-messages-into-a-mysql-database)

> **[Storing MQTT Messages (Sensor Data) in a SQLite DataBase With Python](http://www.steves-internet-guide.com/logging-mqtt-sensor-data-to-sql-database-with-python/)**
>
> In the project we look at how to store our MQTT messages (Sensor.Data) to a Sqlite Database using Python. Storing messages in a database makes them far more accessible.

Personally, i think this is far better than loading a "Ignition MQTT engine" because:

1. You have excellent open source MQTT clients which are well supported and used by a large community.

2. You can eliminate the extra load and risk of running another driver inside Ignition and getting stuck with it forever.

3. MQTT is open standards and evolving rapidly. It's not a proprietary PLC driver. Why should you cough up a big amount for a open standards driver to a proprietary company and suffer under their mercy for ever?.

---

_[View the full topic](https://forum.inductiveautomation.com/t/turn-on-history-on-a-dataset/16944)._