# Ignition Perspective Project Double Logging to SQL **URL:** \ **Category:** Ignition\ **Tags:** database, ignition81, perspective\ **Created:** [February 26, 2025, 6:12pm UTC](https://forum.inductiveautomation.com/t/ignition-perspective-project-double-logging-to-sql/102922 "2025-02-26T18:12:43Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Ryan\_Craig](https://avatars.discourse-cdn.com/v4/letter/r/45deac/32.png) [@Ryan\_Craig](https://forum.inductiveautomation.com/u/Ryan_Craig)\ **Post date:** [February 26, 2025, 6:12pm UTC](https://forum.inductiveautomation.com/t/ignition-perspective-project-double-logging-to-sql/102922/1 "2025-02-26T18:12:43Z")
I have a project that is working fine and running as it should except for it seemed to be double logging to our SQL server. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/0/70039e63bae4342d3a7cd50b8e667c9f7fdc2dfc.png) I am looking into if this could be cause by somewhere inside of the perspective pages/scripting but I just wanted to make sure that my transaction groups aren't causing this for some weird reason. Here are the settings for my transaction groups: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/8/985e57129c59dab8639c311af128f97fed0e1416.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/a/0aa955c1c55974ef3870b153be4ae99963f8c497.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/3/9373b1f736594083c6b9b8b49a23e23f3fc60ced.png) Any information is helpful! ---
**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:** [February 26, 2025, 6:17pm UTC](https://forum.inductiveautomation.com/t/ignition-perspective-project-double-logging-to-sql/102922/2 "2025-02-26T18:17:58Z")
First, make sure you did not create your transaction group in a project that is inheritable. If so, the transaction group will run in each child project that inherits from the parent. ---
**Author:** ![Ryan\_Craig](https://avatars.discourse-cdn.com/v4/letter/r/45deac/32.png) [@Ryan\_Craig](https://forum.inductiveautomation.com/u/Ryan_Craig)\ **Post date:** [February 26, 2025, 6:22pm UTC](https://forum.inductiveautomation.com/t/ignition-perspective-project-double-logging-to-sql/102922/3 "2025-02-26T18:22:23Z")
Just checked and the project is not inheritable. ---
**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:** [February 26, 2025, 6:31pm UTC](https://forum.inductiveautomation.com/t/ignition-perspective-project-double-logging-to-sql/102922/4 "2025-02-26T18:31:02Z")
Maybe try with `Reset trigger after execution` unselected. I think this setting is trying to reset the trigger tag to 0, but it's read only so it reverts to back to 1. ---
**Author:** ![Ryan\_Craig](https://avatars.discourse-cdn.com/v4/letter/r/45deac/32.png) [@Ryan\_Craig](https://forum.inductiveautomation.com/u/Ryan_Craig)\ **Post date:** [February 26, 2025, 7:07pm UTC](https://forum.inductiveautomation.com/t/ignition-perspective-project-double-logging-to-sql/102922/5 "2025-02-26T19:07:46Z")
I tried that out and that doesn't seem to be the issue either. The value seems to reset the trigger correctly back to 0 when the "Reset trigger after execution". I tried turning it off and that value stays 1 and won't continue to log. Another thing I am finding that is curious is all of the repeat logs are logged at the exact same time: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/3/c3b822eea1c6967c4161f4c210900be93594fd08.png) Not sure if this helps in anyway, but it makes me think that something weird is happening that is not script/Perspective related.. If it were script/perspective related, I would imagine the trigger would be turning on then off then on then off again, resulting in two logs at different times.. ---
**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:** [February 26, 2025, 7:12pm UTC](https://forum.inductiveautomation.com/t/ignition-perspective-project-double-logging-to-sql/102922/6 "2025-02-26T19:12:06Z")
Go to the `gateway → Status → Systems → Transaction Groups` and verify that you do not have multiple copies of the same group running. ---
**Author:** ![Ryan\_Craig](https://avatars.discourse-cdn.com/v4/letter/r/45deac/32.png) [@Ryan\_Craig](https://forum.inductiveautomation.com/u/Ryan_Craig)\ **Post date:** [February 26, 2025, 7:17pm UTC](https://forum.inductiveautomation.com/t/ignition-perspective-project-double-logging-to-sql/102922/7 "2025-02-26T19:17:45Z")
Thought I checked that, but after double checking I think that was the issue. I had a backup copy of the program with active transaction groups.. I turned them off, saved, and will start to monitor the SQL data to make sure that was the issue. Kicking myself for overlooking that... thanks for the help!! ---
**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:** [February 26, 2025, 7:33pm UTC](https://forum.inductiveautomation.com/t/ignition-perspective-project-double-logging-to-sql/102922/8 "2025-02-26T19:33:37Z")
Can you mark the post as solved? ---
**Author:** ![Ryan\_Craig](https://avatars.discourse-cdn.com/v4/letter/r/45deac/32.png) [@Ryan\_Craig](https://forum.inductiveautomation.com/u/Ryan_Craig)\ **Post date:** [February 26, 2025, 8:40pm UTC](https://forum.inductiveautomation.com/t/ignition-perspective-project-double-logging-to-sql/102922/9 "2025-02-26T20:40:53Z")
Just did, sorry about that