Is using Resource group to forbid jobs a and b from concurrency but allowing multiple jobs b possible?

Viewed 21

I have a job (job a) that is changing my source database and should not run multiple times at once. Adding to that, I have jobs using it as their data source that do not change the src-db (jobs b). So I want every job a to stop all other jobs from running, but jobs b to be able to be run parallel.

If I add job a and b to a resource group, nothing will run parallel with job a, but I can also only have one job b at once. Is it possible to go around that problem somehow?

I thought about running a job c in a resource group with job a, that runs just to check before a job b - but when the check is over, another job a could be scheduled, so that does not work.

0 Answers
Related