Question

I have a database job that runs occasionally at night and I need a windows service to poll the database regularly to do some more work after the SQL job is done. I am a looking for a solid example to write a scheduler that can fail gracefully without crashing the service.

Was it helpful?

Solution

OTHER TIPS

Just make it a scheduled task. See windows service vs scheduled task

I would use MSMQ, add a final step to the job that adds a message to the queue (Via ActiveX Script / COM or a .net call if you can)

Then have your service monitoring the Queue.

As far as not crashing the service, that would all be up to you and error handling etc...

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top