Aug 30, 2016 07:04 PM|Nataraj Gandhi Arunachalam|LINK
Why not try using a SQL Job which does this? In your table, whenever an update occurs, you can maybe also update another table with a value that the job can check to see if some update had happened. If an update had happened, then your job, when it starts,
it can reset the value in this table and do whatever it needs to do. If no update has occured, it can do the other task that it needs to do. You can configure this job to run every 24 hours.