July 28, 2004 at 1:32 pm
I have a couple of jobs, on a SQL 2000 server, that execute DTS packages that load text files of data into a table. Last night an engineer rebooted the SQL Server at the time that the jobs run. The job status showed 'succeeded', including under 'view job history'. But the data was not loaded.
Event Viewer also did not report a problem. Has anyone else seen Enterprise Mgr report an incorrect job status like that?
July 28, 2004 at 2:36 pm
Haven't seen it, but perhaps the start of the job defaulted to success in the table? Usually if a job doesn't complete, from what I remember, there is nothing in history. Are you sure the success is from last night and not a previous run?
July 28, 2004 at 3:45 pm
I've seen this when a job executes a "dos" command. If the "dos" command fails, the job itself doesn't know it, and completes successfully (the job successfully executed the command). Scheduled DTS packages run from the dos prompt with "DTSRUN" utility, so this may be what you're experiencing????
Steve
July 29, 2004 at 6:29 am
Yes, I'm sure the reported success was not for the previous night.
I guess the 'dos' command explanation is what happened. The DTS package is executed by DTSRUN from xp_cmdshell, but that's from within a stored procedure. The job actually executes the stored procedure as a TSQL-type job step.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply