I have a SQL2005 job that restores some databases that has been running for at least a year with problems.
About a week ago the first restore in the job started taking 10 times longer to run but the following restores seemed to run normally. Thinking that it might have something to do with the database I changed the order and used a different database as step #1. With the order changed and a different database as Step #1 that database took 10 times longer to run and the previous #1 ran as normal.
The entire job does complete but instead of 2 hours it now takes 5 hours.
The other interesting thing is that normally I can "view history" while the job runs and watch as each step executes however now I can't see anything about the job execution until after it has completed.