We've built a report scheduling system using Quartz Scheduler and IBM MQ. Things are working great and we're now getting ready to import scheduled reports from our legacy system into the new.
Our old system, like our Quartz data, is stored in an MS SQL Server Database. The easiest way to migrate the data would be to write an SQL script that pulls the data from our legacy tables and adds them to the Quartz tables.
The Quartz documentation cautions against updating the tables like this and says to use the API instead. I assume this is because if there is an open Quartz scheduler running in code some place it could become out of sync with the database and/or munge the data?
There's no way our DB team would let us run a CLR stored procedure or an executable, so the only other option would be to create a C# web endpoint that would use the API to make the updates.
If we shut down our Quartz scheduling Windows service would we be OK just using an SQL script?
