trouble scheduling jobs

[thack111]

Have any of you ever had trouble with SQL Server 2000, where you build a DTS package and schedule it as a job. It runs great every time till one day it starts only running 1 secont, but still reporting success? This has started happening to me, and since it reports success, I am never notified, and there is no error to try to fix.

Thanks in advance for any help.

Todd

 

[mrdenny]

What happens when you run the package manually? What happens when you run the job manually?

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[thack111]

When I run the DTS package it runs fine, takes 3 minutes to 1 hour depending on the package, if I start the job, it immediatly reports success, and takes about 1 secont.

 

[mrdenny]

What does it say in the job history?
Try deleteing the job, and recreating it manually. See if that helps any.
Try changeing the user that owns the job to the account the SQL Service runs under.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[thack111]

I tried deleting the job and rebuilding it, that had no affect, the user that starts the agent must be the same, but I tried changing the owner of the job to three different users all with full admin rights. I finally did a restart and that has it working again, but this has come up quite a few times, so I don't feel like I fixed anything, and now it will take me 2 ro 3 days to get all my queries caught up, I need to to alert me to just not break.

Thanks,

 

[mrdenny]

What service pack version are you running? You may have a memory leak somewhere.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[thack111]

I am running SQL Server 2000 with Service Pack 3 on Windows NT Server.

 

[mrdenny]

Yeah, there may be a memory leak issue there. I'm not sure. I'd say you should try giving Microsoft a call next time it happens, but I'm not sure they support Windows NT any more.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[thack111]

Well I am supposed to be working on moving to oracle, but it is no small change! Thanks you very much for the info.

Todd

 

[mrdenny]

Moving to Oracle is a major change. Most of you code will need to be rewritten.

Maybe you can get them to cough up the money for a supportable OS for the SQL Server in the mean time.

Denny

--Anything is possible. All it takes is a little research. (Me)