# Historian Table Partitioning

**URL:** <https://forum.inductiveautomation.com/t/historian-table-partitioning/19155>\
**Category:** Ignition\
**Created:** [August 8, 2018, 8:24pm UTC](https://forum.inductiveautomation.com/t/historian-table-partitioning/19155 "2018-08-08T20:24:46Z")\
**Posts on this page:** 1\
**Showing post:** 13

<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:** [August 22, 2018, 9:11am UTC](https://forum.inductiveautomation.com/t/historian-table-partitioning/19155/13 "2018-08-22T09:11:18Z")

</div>

> [@jlteel](#):
>
> I think this is just a limitation of SQL Server or any other database server. When I have tens of millions of rows per table, it's just going to be slow..

Check out this writeup..

> [@Ignition + Apache Kafka =\> Build Massively Scalable Projects - Demo](http://forum.inductiveautomation.com/t/ignition-apache-kafka-build-massively-scalable-projects-demo/19317/2):
>
> Let’s build a Big Data Kafka client module for Ignition – "IgnitionKafkaClient.modl": Why do we need a “Big Data Kafka client” for Ignition?: Few years back, most of us would have never imagined a SCADA project generating and logging millions of records per day into a historian database. Today, Big Data has become the hottest topic among SCADA professionals including this forum. Even highly accomplished SCADA veterans are becoming bit nervous and taking a back step when this topic is opened up…

---

_[View the full topic](https://forum.inductiveautomation.com/t/historian-table-partitioning/19155)._