Be carefull when using the sysinternals handle executable as part of a SQL Server Job. For more details see:
Formum post but noone has replied:
SQL Server 2000 has an Agent service that can run jobs that can perform file manipulation and a frequent problem is that the file is open by another process. An example is a job to perform database backups which also deletes prior backups that are older than a specified criteria. I have set up a SQL Server jobs that runs handle.exe when the database backup job step fails.
Handle version 3.02 works fine but handle v3.20 cause the SQL Server job to hang, that is, the SQL Server Job status is executing and it never finishes. This hang does not occur when handle is run as a windows scheduled task.
SQL = Scarcely Qualifies as a Language