I have developed a custom timer job, inheriting from SPJobDefinition. It currently runs on two content databases, and I would like it to run on only one.
I have created this timer job using the following constructor:
public HiddenTitleJob(string jobName, SPWebApplication webApplication) :
base(jobName, webApplication, null, SPJobLockType.Job)
{
this.Title = "Hidden Title Timer Job";
}
Many web sources, including this question, seem to suggest that SPJobLockType.Job prevents my timer job from running on more than one content database, but it hasn't worked for me. Microsoft's documentation is very vague, it only says "Locks the job to prevent it from running on more than one machine" - it says nothing about content databases.