# Autoincrementing indexes

**URL:** <https://forum.inductiveautomation.com/t/autoincrementing-indexes/3519>\
**Category:** Ignition\
**Created:** [October 28, 2011, 6:07pm UTC](https://forum.inductiveautomation.com/t/autoincrementing-indexes/3519 "2011-10-28T18:07:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Greg.Buehler](https://avatars.discourse-cdn.com/v4/letter/g/ecc23a/32.png) [@Greg.Buehler](https://forum.inductiveautomation.com/u/Greg.Buehler)\
**Post date:** [October 28, 2011, 6:07pm UTC](https://forum.inductiveautomation.com/t/autoincrementing-indexes/3519/1 "2011-10-28T18:07:10Z")

</div>

I was wondering if Ignition does any indexing internally that would become an issue in a scenario where the databases are configured for replication.

For example, if I changed DB1 to work on increments on the pattern 1, 11, 21, 31, etc and DB2 to work on increments of 2, 12, 22, 32, etc would there be any issues?

---

<div class="post-metadata">

**Author:** ![Travis.Cox](https://avatars.discourse-cdn.com/v4/letter/t/b9bd4f/32.png) [@Travis.Cox](https://forum.inductiveautomation.com/u/Travis.Cox)\
**Post date:** [October 28, 2011, 6:11pm UTC](https://forum.inductiveautomation.com/t/autoincrementing-indexes/3519/2 "2011-10-28T18:11:30Z")

</div>

No, the only way we would use the index is for finding the first or last row. We mostly use timestamps in our queries.