# What is the Best way to define Shifts using db Time Stamp

**URL:** <https://forum.inductiveautomation.com/t/what-is-the-best-way-to-define-shifts-using-db-time-stamp/41303>\
**Category:** Ignition\
**Tags:** database, ignition79\
**Created:** [December 8, 2020, 5:18pm UTC](https://forum.inductiveautomation.com/t/what-is-the-best-way-to-define-shifts-using-db-time-stamp/41303 "2020-12-08T17:18:56Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![dkhayes117](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dkhayes117/32/68344_2.png) [@dkhayes117](https://forum.inductiveautomation.com/u/dkhayes117)\
**Post date:** [December 9, 2020, 1:05pm UTC](https://forum.inductiveautomation.com/t/what-is-the-best-way-to-define-shifts-using-db-time-stamp/41303/4 "2020-12-09T13:05:18Z")

</div>

I added a shift column in my database, which the transaction group logs to along with work data. That way I can use Ignition schedule management tool. I create a “user” for each shift, then run a timer script to check if they are currently scheduled or not, then write to a bool memory tag. It may seem a little hacky, but it has worked without fail for me.

[Shift Work Schedules - Ignition - Inductive Automation Forum](http://forum.inductiveautomation.com/t/shift-work-schedules/19848/10)

---

_[View the full topic](https://forum.inductiveautomation.com/t/what-is-the-best-way-to-define-shifts-using-db-time-stamp/41303)._