# SQLite DB failed to load after polling rate

**URL:** <https://forum.inductiveautomation.com/t/sqlite-db-failed-to-load-after-polling-rate/53621>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [December 1, 2021, 2:42pm UTC](https://forum.inductiveautomation.com/t/sqlite-db-failed-to-load-after-polling-rate/53621 "2021-12-01T14:42:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [December 1, 2021, 3:29pm UTC](https://forum.inductiveautomation.com/t/sqlite-db-failed-to-load-after-polling-rate/53621/3 "2021-12-01T15:29:49Z")

</div>

> [@SKA](#):
>
> SQLite is what it says in the name, lite, it will not perform like MS SQL Server or MySQL.

This. Use a real database. A SQLite DB, fundamentally, is a generic configuration file manipulated with SQL. Its codebase is optimized for compact single file storage and a minimalist library footprint. It is not and never will be suitable for Tag History in any ordinary sense.

If you want maximum utility in a free database, I recommend PostgreSQL. I think MariaDB is also a good choice.

---

_[View the full topic](https://forum.inductiveautomation.com/t/sqlite-db-failed-to-load-after-polling-rate/53621)._