July 15, 2004 at 9:42 am
Hello
I have a nightly processs that runs an extract from a SYBASE 5.0 ODBC connection through a SQL 7.0 server to create a text file to FTP to UNIX
I use SQL server because it is mine and the other 2 boxes a not. (corporate america)
When I run the selection to the Sybase box I occasioanlly get hung up teh DTS doesn't finish continues to look as though it is running.
I can cancel and run and it will work.
I have use OLE service component unchecked and my priority set to high
Any ideas.
Can I evaluate the fact that it is running 1/2 hour after starting cancel and restart with another job??
This has also happened going to DB2 in the past.
July 15, 2004 at 1:17 pm
I'm going to guess that you have this scheduled as a job?
If so, and you go into the Jobs under SQL Server Agent, you may have to refresh the screen to be able to view changes. SQL Server does not always update this screen view automatically.
This has tripped me up on occassion where I thought that it was still running but it actually was not.
However, you say that you cancel the job and then re-run and if it currently is not running, MS-SQL will raise an error stating this fact, so maybe this is not your case.
I have several jobs that run against DB2 and the run time can really vary based on the load on DB2 at the time. The job may not actually be hanging, just that the source system is loaded down not allowing the existing execution to finish, and when you stop it and re-execute the same query, resources on the box are now different allowing it to finish.
Just a thought.
July 16, 2004 at 8:34 am
It is scheduled as a job.
There is no activity on the processors.
The job status is 1 and it is on the DTS step.
FYI
I have created an evaluation job with a threshold of normal runtime + 10 minutes that will run every 10 minutes and will sp_stop_job
wait
sp_start_job
This seems to work.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply