Historian Table Partitioning

Ignition
21

Hi Jeff,

MS SQL is known to have problems with index fragmentation on big tables.

Perhaps it’s worth to read this, and check out if it matches with your problems.

https://docs.microsoft.com/en-us/sql/relational-databases/indexes/reorganize-and-rebuild-indexes?view=sql-server-2017

1 Like
22

We are using Linux and MariaDB with tokuDB engine for performance reasons. On our first large ignition job back in 2014 we originally planned for Windows server and MS SQL Server but Kyle Chase recommended this setup for performance reasons, so we went this direction.
The server is a VM on VMWare, allocated 2 processors of 6 cores each, ram (um) 400GB but 100GB appears to be in use, from 2014-2017 it was 16GB and running okay.

I'm no expert on databases but the Fractal Tree Indexing TokuDB uses often gets credited with maintaining speed on large tables because it doesn't fragment.

2 Likes
23

In this case, please consider using a real-time database, for example CanaryLabs Historian or Kepwaer Local Historian.

1 Like