Can you check below things
1) Run the query from the db connect ui to see it goes through fine
2) Make sure ID is not alphanumeric and is unique and is incremental
3) can you hardcode the id to start off with for example id>1234 such that intial load knows where to start from and then it takes off from there
4) Once the schedule run is complete, look for data in the index for "All Time" , as it is possible that the events are back dated depending on which column is being treated as event date
5) Make sure you have date column available in the table, if you already have an date column which you would want to use as event date, make that column as the first column( select a.modify_time as event_date , a.* from table1 a where id>1234) , if you do not have date column you may use currentimestamp as event_date, I would call it out explicitly though I know splunk would use upload time as event date just to make sure no other column is playing spoilsport.
6) none of these work, then check you error logs and debug options as suggested by Dave.
... View more