1

I had a large update statement run over the weekend that took approximately 6.5 hours to complete. That was 2 days ago (friday evening, today is monday morning). The table has 77million records in it, and about 10 fields were updated. Monday morning I logged in to check my update results and the table is locked. I have a COMMIT TRANSACTION at the end of the stored procedure, so I don't know what is goig on with the table?

I don't want to kill the SPID either, because it might roll back whatever it is doing.

Help! What can I do to get

Thanks in advance.

MadHatter
  • 81,580
EWizard
  • 11

1 Answers1

1

If it's still running, you have two options: let it finish and commit the work, or kill the process and thus roll back the transaction.

If it's finished, and it just didn't commit the open transaction for whatever reason, find the system that connection is from so you can manually commit the transaction rather than killing it and rolling back.

db2
  • 2,180