# Docker and SQLite

**URL:** <https://forum.inductiveautomation.com/t/docker-and-sqlite/53678>\
**Category:** Maker\
**Tags:** ignition81\
**Created:** [December 2, 2021, 4:08pm UTC](https://forum.inductiveautomation.com/t/docker-and-sqlite/53678 "2021-12-02T16:08:20Z")\
**Posts on this page:** 1\
**Showing post:** 10

<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 3, 2021, 2:06pm UTC](https://forum.inductiveautomation.com/t/docker-and-sqlite/53678/10 "2021-12-03T14:06:16Z")

</div>

> [@deon.korb](#):
>
> The performance of the handful of tags to the SQLite DB is not great and I get a lot of log errors with file locked etc.

This is no surprise. SQLite just isn't made for the Tag History use-case. Recent discussion on SQLite:

> [@SQLite DB failed to load after polling rate](https://forum.inductiveautomation.com/t/sqlite-db-failed-to-load-after-polling-rate/53621/3):
>
> 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/docker-and-sqlite/53678)._