June 18, 2009 at 9:08 am
I want to end a job that is running but it is wrapped in a transaction. Is there any way for me to end the job and still have it commit what has been processed so I don't have a huge rollback?
I'm having disk queu issues related to the job 🙁
Thanks for your help!
June 18, 2009 at 9:15 am
No. If you kill it, you will encounter the rollback.
I would recommend breaking up the job into smaller chunks so that it doesn't process as much at once, or so that it will process in stages with each stage being a transaction - if possible within the requirements of the job.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
June 18, 2009 at 9:37 am
ugh - was hoping there was some slick unknown method for doing this - hack the lsn and commit it or something.
Yes, I will have to look at re-engineering it. Unfortunately the biggest issue is the intermittent lock on the table I'm deleting from due to services that are still running against it - of which, I cannot stop.
Thanks for your feedback!
-Sandy
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply