# Adjustable alert time deadband **URL:** \ **Category:** Ignition\ **Created:** [March 5, 2012, 9:47am UTC](https://forum.inductiveautomation.com/t/adjustable-alert-time-deadband/4103 "2012-03-05T09:47:20Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Ruslan](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@Ruslan](https://forum.inductiveautomation.com/u/Ruslan)\ **Post date:** [March 5, 2012, 9:47am UTC](https://forum.inductiveautomation.com/t/adjustable-alert-time-deadband/4103/1 "2012-03-05T09:47:20Z")
Hello! It is required in our project to make time deadband on specific alarms adjustable. As far I can see, it is fixed at the moment. Is there any way to make it tag driven, like value deadband? Or is there any other mean to make it adjustable? Only way I can think of is gateway script, but this solution requires a DB storing times of my alarm tags and I don’t like it in general. Thanks in advance. ---
**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:** [March 5, 2012, 3:03pm UTC](https://forum.inductiveautomation.com/t/adjustable-alert-time-deadband/4103/2 "2012-03-05T15:03:35Z")
When the tags are stored in the internal database you only edit the alert time deadband through the designer. You cannot make them dynamic or tag driven. However, you can store your tags in an external database where you can dynamically change any configuration of the tag. Tag a look at this page on external SQLTags providers: [http://www.inductiveautomation.com/support/usermanuals/ignition/database\_driving\_provider.htm](http://www.inductiveautomation.com/support/usermanuals/ignition/database_driving_provider.htm) ---
**Author:** ![Ruslan](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@Ruslan](https://forum.inductiveautomation.com/u/Ruslan)\ **Post date:** [March 19, 2012, 11:20pm UTC](https://forum.inductiveautomation.com/t/adjustable-alert-time-deadband/4103/3 "2012-03-19T23:20:08Z")
Thanks, your advice actually was useful, but when I implemented suggested solution, some confussion appeared. When I changed alarm time deadband directly in DB, and then tried to check if it worked in “edit tag(s)” window, it remained the one before change. Then I changed it in that window, and it was successfully wrote to DB. Why does this mechanism work in one way? Oh, now it came to my mind, that I probably forgot to refresh the SQLTags Browser, may this be the cause? ---
**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:** [March 19, 2012, 11:49pm UTC](https://forum.inductiveautomation.com/t/adjustable-alert-time-deadband/4103/4 "2012-03-19T23:49:48Z")
No, it is that you must alter the configchange column in order for Ignition to see config changes. You need to also run the following query:`UPDATE sqlt_core SET configchange = CURRENT_TIMESTAMP WHERE id = ?` ---
**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\ **Post date:** [March 21, 2012, 1:09pm UTC](https://forum.inductiveautomation.com/t/adjustable-alert-time-deadband/4103/5 "2012-03-21T13:09:46Z")
Just want to make a note , this works in V7.3.X, but I was using V7.4 RC1 or 2, the service had to be stopped and started for changes to take effect. ---
**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:** [March 21, 2012, 5:00pm UTC](https://forum.inductiveautomation.com/t/adjustable-alert-time-deadband/4103/6 "2012-03-21T17:00:46Z")
You shouldn’t have to restart Ignition to make config changes. I will look into it for 7.4. Thanks for reporting that.