Home/ Questions/Q 3315208
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T22:19:24+00:00

I use a TransactionScope in a thread to dump data in my SQL Server

  • 0

I use a TransactionScope in a thread to dump data in my SQL Server database.

using (TransactionScope scope = new TransactionScope())
{
    // Dump data in database
    scope.Complete();
}

The transaction is a long transaction (~40 seconds) because the large amount of data. This is normal.

When I do an Abort() to stop the thread during this transaction, SQL Server seems to be locked for a few minutes.

What is happening and how can I avoid this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Simply said: you can not.

    Server seems to be locked during a few
    minutes.

    No. SQL Server is busy undoing your transaction. It is optimized fully to COMMIT transactions, not to undo them. Undoing LARGE updates is a SLOW operation. Depending on your server layout and the amount of data it can take some minutes or even hours.

    All you can do is… not rollback / abort. Or wait.

    • 0