Nice procedure. However, I'd use some sort of flagging instead of a GOTO loop. If you combine the SET assignment with a query, you can return the status with extra variables.

eg:
WHILE @myFlag = 0
BEGIN
  -- check if job has completed
  SET @jobresult= ISNULL(SELECT b.last_run_outcome
    from msdb.dbo.sysjobservers b (nolock)
    where  b.job_id=@Jobid
    and convert(varchar(12),last_run_date,121)>=@lastrundate
    and last_run_time>=@lastruntime), -1) 
  IF @jobresult <> -1
    SET @myFlag = 1

END

Also, under what security context does this procedure get called, and how does that affect running the jobs?

The dammed thing is that the great SQL Server scheduler is not available

in MSDE SQL 2005 (aka SQL Express).

regards

Baudewijn Vermeire

Control-M batch scheduler is a enterprise batch management solution that is used to run and mantain external jobs .

This is a product developed by BMC Software .

Windows built-in Task Scheduler works great for scheduling and running DTS packages via the DTSRun utility. It even allows you to specify the Windows account to run it under. This comes in especially handy because it allows me to use external executables without installing them on the SQL Server.

Sureshkumar,

I'm curious why you did not include SQL's native Multi-Server administration system that allows you to schedule, monitor, and report on jobs from a centralized server (MSX the Master) of other SQL servers (TSX Targets).

Thanks...Nali