I am currently rebuilding our antiquated batch process using the SQL job scheduler and have run into a small issue. When a Stored procedure is executed as a job step and any message is sent back other than "Number of rows affected" the job does not terminate. I can get the procedures to run by building it first as a DTS package and then scheduling it as a job but I would like to avoid this step if possible. The same thing occurs with a test exe written to fail. The exe gets a popup box that requires that you click ok....DTS works Job Scheduler hangs.
Any ideas....
Thanks,
Judie
Any ideas....
Thanks,
Judie