SQL005 Jobs Not working as normal

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.  

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Guy Hengel [angelIII / a3]Billing EngineerCommented:
if changing the db order does not reproduce the issue on the same database, the issue is somewhere else.
I would guess it's the disk where the restores are stored on: initial access time being changed (or the destination disk ...)

is the backup source on a dedicated disk? anything changed about that disk?
Eugene ZCommented:
please clarify:

1. "restores some databases"  - does it affect all DBs or some?
2. how fast runs backup for the "slow" restores?
3. is it the same server for bkps \restore?
4. where is the backup files location?
5. how big the "slow" dbs size? was it changed since the last "fast" run?
6. are there any related errors in the event viewer\sql errorlog?
7. is there enough cpu\memory?
8. is it native sql backup or 3rd party ?
9. if 3rd- is it compressed?
10. when did you reboot this box last time?
11. are you running anything during the "bad" time: another sql jobs? antivirus? etc
jdr0606Author Commented:
It does not appear to be job related most likely resource issues.  The steps in the job run OK some nights and much more slowly other nights.  i.e. last Wednesday night the entire job took 2:45 minutes (normal), Thursday night it took over 5 hours and Friday night 5.5hours.

Currently looking at resources other than SQL which I no longer believe is a factor.

Thanks for the input.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jdr0606Author Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for jdr0606's comment #a39478079
Assisted answer: 250 points for angelIII's comment #a39459312
Assisted answer: 250 points for EugeneZ's comment #a39462138

for the following reason:

While the input from the experts was helpful, at the end of the day it was determined to be something not likely related to the original request.
Eugene ZCommented:
just ignore this - wrong post
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.