# Ignition 8.1.2 SQL Tags Not Updating After Update From 7.9

**URL:** <https://forum.inductiveautomation.com/t/ignition-8-1-2-sql-tags-not-updating-after-update-from-7-9/43418>\
**Category:** Ignition\
**Created:** [February 15, 2021, 1:41pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-2-sql-tags-not-updating-after-update-from-7-9/43418 "2021-02-15T13:41:43Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [February 15, 2021, 2:45pm UTC](https://forum.inductiveautomation.com/t/ignition-8-1-2-sql-tags-not-updating-after-update-from-7-9/43418/7 "2021-02-15T14:45:17Z")

</div>

1. Gateway project scope instead of gateway global scope.
2. Option for a dedicated thread.
3. Single event script can run multiple queries in any desired order, writing results to memory tags with any desired timing.
4. Event scripts can post-process results before writing to tags, relieving the DB of static joins and other lookups. Including using cached lookups.
5. Event scripts can drive multiple target tags from single, larger queries.
6. Event scripts can simulate joins across datasources.
7. Easy parallelism control with separate event scripts.
8. Even when not using a dedicated thread, gateway events use a different thread pool than tag groups and tag events.

Edit:  
9) Tag groups (and v7.9 scan classes) are operationally opaque–very un-fun to troubleshoot.

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-8-1-2-sql-tags-not-updating-after-update-from-7-9/43418)._