Hi everyone.
I have a SQL job in which the last step calls an outside cmd batch. This ba
tch often gets suspended indefinitely. In order to allow the SQL job to com
plete I periodically run a scheduled command that kills the suspended batch.
This allows the SQL job t
o end, but it does not end it in a failure. The job reports successful exec
ution. Is there a creative way to force the job to return failure status in
this case?
I appreciate your help
OscarIs there a way that you could include some commands within that non-SQL job
that will handle the timeout?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment