1 of 1 people found this helpful
Hi Sean. You'll need the data describing when db loads complete, with a date/time representing the completion time. Connect to that data, filter it to a relative date of "Last Hour" (for example), then subscribe to it on an hourly VizAlerts schedule. Now your trigger view will have data in it if the db load completed in the previous hour, and it will run. If you aren't satisfied with it running up to an hour later than the db load actually completes, you can tighten the relative date window down and increase the schedule cadence. After the db load completes, and the alert fires, it will not fire again until the next db load (that is, until the date/time field occurs within the last relative time interval again). This mechanism is one of the most critical techniques used for most of our own VizAlerts to avoid continual duplicate alerts going out.
Triggering a schedule via tabcmd should have no effect on VizAlerts, unfortunately, because it's only looking for the scheduled next run time, and comparing that to when it recorded that it last ran the alerts on that schedule.
You have saved me some time trying the tabmd option. I would have tried that first. I'll look for or create a source of when the db loads complete instead and try that method.