October 10, 2007 at 5:48 am
I have a scheduled DTS package that has been running for 24 hours. The reason for that is a stored procedure within it that inserts new and updates old performance for 19000 rows. There is a maximum of 10 performance items to insert or update but they are usually not all there. For this particular client, it takes a very long time to run although another client with a slightly larger number of rows it only takes a few minutes. It first does its battery of insersts, which are already done, and then proceeds to the updates. The result of sp_who2 show that the process is at the update stage but, checking the data, it appears to have completed it. I am apprehensive of killing this job because of the rollback that would cause the loss of the data already processed. Would there be a way to force this data to commit and then kill the job?
Thanks,
Ed
October 10, 2007 at 7:17 am
The 😀 job completed after 26 hours so there is no urgency to this anymore but I am still curious if it can be done.
Regards,
Ed
October 10, 2007 at 7:50 am
I think you need to provide more information about exactly the code being run. It's not clear from your post what's happening.
Jobs don't run from clients. They run from the server.
October 10, 2007 at 7:59 am
The jobs run a DTS package but it's in the performance stored procedure that the main one gets stuck. The other one I run it directly from DTSDesigner because it takes so little time but this one runs from a job because of the time. The DTS package that doesn't take too long is fully integrated. Extraction, Transform and Load are in the same package. The long running one consists of three packages: Extract, Transform and Load. I run from DTSDesigner the first two and schedule the Load step. What information can I give you?
Thanks,
Ed
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply