Hi,

A job is running every minute.

Sometimes a #300 "Cannot lock the table Tasks in the schema Default for exclusive access" is shown in LogEvents and I suspect it is coming from this job.

1. What happens when a job is not finished after one minute? Does the job create an new instance while it it still running?

2. Does the job lock the complete database when there is no specific transaction and if so would it help to add a "start transaction" with only the tables which are updated so the timeperiod for locking is limited?

Regards,

Mike

Mike,

<< Sometimes a #300 "Cannot lock the table Tasks in the schema Default for exclusive access" is shown in LogEvents and I suspect it is coming from this job. >>

Are you trying to alter an existing table ?  The only functionality that tries to lock a table for exclusive access is/are the DDL statements.

<< 1. What happens when a job is not finished after one minute? >>

A job will keep trying for the duration of its scheduled time range.  However, "trying" consists of only creating a fire-and-forget thread that will try to run the job and then terminate.

<< Does the job create an new instance while it it still running? >>

No.

<< 2. Does the job lock the complete database when there is no specific transaction and if so would it help to add a "start transaction" with only the tables which are updated so the timeperiod for locking is limited? >>

No, transactions don't have anything to do with exclusive locks, so they are not applicable in this case.

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

Thank you for the explanation.

There are no tables altered so there must be something else causing this.