This trigger is automatically created when using SignalR or SQL table dependency for real-time synchronization. We cannot identify which one is currently being used. We have an option to check the trigger at certain intervals and then place the new trigger there and remove the old one. I don't know how accurate this will be, it's a guess solution.