Kim Crosser (11/27/2015)

---

TomThomson (11/26/2015)

---

I would have a simple approach to Kim's problem: inform management that the only reasonable way I - as a database person - could resolve this problem would be to create a trigger which would cause an app failure when a modification was made to the database that introduced this inconsistency. It would then be possible to determine which part of which app was doing what when the failure occurred. The alternative would be to have the application developers do the work necessary to discover where their code was doing the wrong thing - perhaps it would be possible for them to do this in a non-disruptive manner.

While that would at least give some additional information as to the processes involved where the error occurs, the production system is a 7x24 Public Safety system. Any trigger or other trap that causes a user-visible error and prevents an officer from completing his/her job isn't allowed. Besides - it would likely fire at 0300 on a Sunday, triggering help desk and other support calls. :w00t: So - back to debugging through code analysis.