PHWinfo - Afficher un message

27/03/2008, 23h36

>>
I could just check the job status every second.
>>

Ugh. If the job takes 20 minutes to run, then that is a LOT of wasted
resources. Why not update a flag somewhere only when the job has completed
(with a job you can mark this whether or not the originating step
succeeded)?

27/03/2008, 23h36	#5
Aaron Bertrand [SQL Server MVP] Messages: n/a Hébergeur:	Re: Calling a sql job synchronously >> I could just check the job status every second. >> Ugh. If the job takes 20 minutes to run, then that is a LOT of wasted resources. Why not update a flag somewhere only when the job has completed (with a job you can mark this whether or not the originating step succeeded)?