# Alert\_log index

**URL:** <https://forum.inductiveautomation.com/t/alert-log-index/1499>\
**Category:** Ignition\
**Created:** [February 5, 2010, 3:35pm UTC](https://forum.inductiveautomation.com/t/alert-log-index/1499 "2010-02-05T15:35:09Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![david\_mccutchen](https://avatars.discourse-cdn.com/v4/letter/d/919ad9/32.png) [@david\_mccutchen](https://forum.inductiveautomation.com/u/david_mccutchen)\
**Post date:** [February 5, 2010, 3:35pm UTC](https://forum.inductiveautomation.com/t/alert-log-index/1499/1 "2010-02-05T15:35:09Z")

</div>

Is there a reason that there is no “id” index on the alert\_log table? In our legacy system we look at alarmlog\_ndx to determine the row we are updating. Is it ok to add an id index to this table?

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [February 5, 2010, 5:20pm UTC](https://forum.inductiveautomation.com/t/alert-log-index/1499/2 "2010-02-05T17:20:25Z")

</div>

I’ll have to check, but it is probably an oversight.

Feel free to add an auto-increment ID to the table.

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [February 7, 2010, 5:24pm UTC](https://forum.inductiveautomation.com/t/alert-log-index/1499/3 "2010-02-07T17:24:35Z")

</div>

If you do create it by hand, I’d recommend using the same convention that FactorySQL used (“tablename\_ndx”). It is almost certainly an oversight (although, it might have been on purpose, since an INT id doesn’t get used much with alerts- they’re always queried/ordered based on timestamp), and if/when we fix it, it will use that scheme.

Regards,

---

<div class="post-metadata">

**Author:** ![DarrenAsh](https://avatars.discourse-cdn.com/v4/letter/d/779978/32.png) [@DarrenAsh](https://forum.inductiveautomation.com/u/DarrenAsh)\
**Post date:** [February 21, 2010, 3:18pm UTC](https://forum.inductiveautomation.com/t/alert-log-index/1499/4 "2010-02-21T15:18:49Z")

</div>

I am really new to this, but I ran into this with the example ignition project and the alarm table.  
The ID column looks important if you want to easily ACK a single row in the alarm history table. Of course there are a lot of other mismatches to the original alert table format compared to the new, but that just helped me understand it a little better by getting it to work.

General question, is there a way to get it to stop popping up the error boxes during design mode? This gets annoying when you are trying to look through the window elements and there is an error on a query that keeps firing.

Thanks,

Darren

---

<div class="post-metadata">

**Author:** ![Robert.McKenzie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/robert.mckenzie/32/4134_2.png) [@Robert.McKenzie](https://forum.inductiveautomation.com/u/Robert.McKenzie)\
**Post date:** [February 22, 2010, 7:54pm UTC](https://forum.inductiveautomation.com/t/alert-log-index/1499/5 "2010-02-22T19:54:54Z")

</div>

You can keep the error box from popping up every time a new error triggers by minimizing it. Just click on the arrow in upper right of the window that points down and left. The error box will then happily sit in your task bar without bothering you until you open it again.