You can change the schedule of ExecuteSql Processor
Right Click --> Configure --> Scheduling tab
Executesql either trigger based on Timer driven (or) cron driven, as shown in the above RunSchedule 1111111110 sec means the processor trigger once 1111111110 sec. you can use like 1 min,1 hr instead of specifying in sec.
Cron driven use this link to make your cron expression then change the scheduling strategy to cron driven and keep your cron expression in Run Schedule.
ExecuteSql processor doesn't store the state if you want to incrementally pull the data then use either incremental fetch using QueryDatabaseTable (or) Generate Table Fetch processors as these processors stores the state based on max value column provided and pulls only the changes made after the store state.
You can change the schedule of ExecuteSql Processor
Right Click --> Configure --> Scheduling tab
Executesql either trigger based on Timer driven (or) cron driven, as shown in the above RunSchedule 1111111110 sec means the processor trigger once 1111111110 sec. you can use like 1 min,1 hr instead of specifying in sec.
Cron driven use this link to make your cron expression then change the scheduling strategy to cron driven and keep your cron expression in Run Schedule.
ExecuteSql processor doesn't store the state if you want to incrementally pull the data then use either incremental fetch using QueryDatabaseTable (or) Generate Table Fetch processors as these processors stores the state based on max value column provided and pulls only the changes made after the store state.
