Hey Shan,
I’m 4 years late with the solution, but hopefully this is of use to you. We recently hit the same issue, and I have an aversion to third party solutions, as this normally means extra cost, less support, and more complexity. However, I’ve just spoken with a consultant who’s provided a great fix.
Use the normal SQL adapter to poll the SQL Server on which BizTalk’s data is hosted (or any SQL Server DB), and have this call the command “select 1”. This will always return a result, so will always trigger your orchestration. Set this port up so that Poll While Data Found is false (to save flooding your orchestration), and setting the polling interval as required. This gives you the scheduling functionality with a fully biztalk friendly method, and no extra expense.
Hopefully that’ll help out anyone with similar issues in the future.
Kind regards,
JB