# Ensuring unique serialization per part type across multiple stations/machines

**URL:** <https://forum.inductiveautomation.com/t/ensuring-unique-serialization-per-part-type-across-multiple-stations-machines/103730>\
**Category:** General Discussion\
**Tags:** database, datascience\
**Created:** [March 14, 2025, 8:50pm UTC](https://forum.inductiveautomation.com/t/ensuring-unique-serialization-per-part-type-across-multiple-stations-machines/103730 "2025-03-14T20:50:06Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [March 14, 2025, 9:07pm UTC](https://forum.inductiveautomation.com/t/ensuring-unique-serialization-per-part-type-across-multiple-stations-machines/103730/4 "2025-03-14T21:07:10Z")

</div>

> [@ryan.white](#):
>
> options

In such a case, I'd make a separate table for each part type for the sole purpose of treating its auto-increment column as the serial. Use an insert trigger on each part type table to copy the whole row + constant part type ID to the main table. Carry on with the main table. (Can prune the separate tables after the main table is updated. Perhaps place the part type tables in their own schema to avoid misuse.)

---

_[View the full topic](https://forum.inductiveautomation.com/t/ensuring-unique-serialization-per-part-type-across-multiple-stations-machines/103730)._