There are many possible solutions to this.
The "cleanest" one is to separate the databases so that your local application won't connect to the database of the dev server at all and will maintain some database running locally.
Another possible solution is to refactor the scheduled job to run only upon some kind of custom configuration so that on dev profile (you might use spring profiles or 'conditions' in code) the scheduler won't run at all. On the dev server this configuration will be enabled by default and the scheduling will run as usual.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…