SQL Server Performance Forum – Threads Archive

Steps out of order in starting schedule job

Hi everyone, Does anyone notice on enterprise manager, when starting the schedule job by right click the job – start job, sometimes the steps are in order and sometimes are out of order? This hasn’t been a problem until applying Service Pack on SQL Server 2000, which may be on SP3. Does anyone have suggestion on how to fix it? Any ideas or comment are greatly appreciated. Have a good weekend! Regards, [<img src=’/community/emoticons/emotion-1.gif’ alt=’

‘ />][^] Paulus

First time I see that problem. Did you try to re-create the job?
Luis Martin
Moderator
SQL-Server-Performance.com

I’ve never seen it either. When this happens have you gone back into edit the job to see what the order is in there? Are you sure the correct step is set to start first?

Does the job involves network transactions like file copy etc.
What kind of code used to execute in the job steps? If that job involves a DTS package to execute then take help package logging by DTS Enable Package Logging from EM. If not refer to SQLAgent Log for full information and also can take help of PROFILER for a detailed view of activities during this process. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

Thanks for all of your response. I appreciate it. From Luis response, I did not recreate the jobs. I think recreating the job may not help, because the problem happen on any job with more than 3 steps. EVEN THOUGH THE JOB RUN IN ORDER, the display of step during job start give confusing look as if the job will run out of order. For example on 3 steps job, it display 1 – 3 – 2. From Chris response, I checked the step detail, and everything in orderly display. The start step drop down menu shown (1)Step Name, and on the white box step listing, the step 1 has green mark. From Satya response, yes, our job involve network copy using DOS batch Copy command, but this problem happen also in other DOS batch job like running OSQL command line. The steps in the job involve using several DTS packages, but turning DTS log may not help, because the log only record the DTS activity on that step only. This is the log that is activated through EM – Local Package – open the package – package property Paulus

How about references from SQLAgent log and running PROFILER during this process is scheduled.
If the network transaction is included then ensure there are no issues with network during this operation. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided â€œAS ISâ€ with no rights for the sake of knowledge sharing.

]]>