Hello,

Is it possible that somebody e.g. a SQL Server Administrator, has recently changed the query governor cost limit?

I am just wondering why your job was working before, and not now. Have there been any other major changes on the Server e.g. a large increase in data volume or removal of indexes that might cause the job to run a lot longer than before?

Regards,

John Marsh