HELP - need to kill big transaction that's taking too long to rollback

Hi all,
I have a big transaction running on a table that I had to kill and
rollback. Unfortunately, the transaction has been rolling back for 1.5
hours and is supposedly only 6% done rolling back. I need to stop this
transaction, and I'm looking for the fastest way to do it with doing
the least amount of damage.
Is there any nuke button that I can press to kill this process with
extreme prejudice? - at this point I don't care about the integrity of
the table I was running the transaction on - I just want it to die.
Is there any way to force the table to drop, thus killing the process?
Is there any way to make a new log file for this database, and kill the
log file that has the rolling back?
If I stop SQL Server, will it try to wait until the transaction is
done/rolledback before it will actually stop?
Please HELP! Thanks in advance
-Rob
Stop the server service?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"robh1999atgmail" <RobH1999@.gmail.com> wrote in message
news:1159460802.483348.29370@.d34g2000cwd.googlegro ups.com...
> Hi all,
> I have a big transaction running on a table that I had to kill and
> rollback. Unfortunately, the transaction has been rolling back for 1.5
> hours and is supposedly only 6% done rolling back. I need to stop this
> transaction, and I'm looking for the fastest way to do it with doing
> the least amount of damage.
> Is there any nuke button that I can press to kill this process with
> extreme prejudice? - at this point I don't care about the integrity of
> the table I was running the transaction on - I just want it to die.
> Is there any way to force the table to drop, thus killing the process?
>
> Is there any way to make a new log file for this database, and kill the
> log file that has the rolling back?
> If I stop SQL Server, will it try to wait until the transaction is
> done/rolledback before it will actually stop?
> Please HELP! Thanks in advance
> -Rob
>

HELP - need to kill big transaction that's taking too long to rollback

Hi all,
I have a big transaction running on a table that I had to kill and
rollback. Unfortunately, the transaction has been rolling back for 1.5
hours and is supposedly only 6% done rolling back. I need to stop this
transaction, and I'm looking for the fastest way to do it with doing
the least amount of damage.
Is there any nuke button that I can press to kill this process with
extreme prejudice? - at this point I don't care about the integrity of
the table I was running the transaction on - I just want it to die.
Is there any way to force the table to drop, thus killing the process?
Is there any way to make a new log file for this database, and kill the
log file that has the rolling back?
If I stop SQL Server, will it try to wait until the transaction is
done/rolledback before it will actually stop?
Please HELP! Thanks in advance
-RobStop the server service?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"robh1999atgmail" <RobH1999@.gmail.com> wrote in message
news:1159460802.483348.29370@.d34g2000cwd.googlegroups.com...
> Hi all,
> I have a big transaction running on a table that I had to kill and
> rollback. Unfortunately, the transaction has been rolling back for 1.5
> hours and is supposedly only 6% done rolling back. I need to stop this
> transaction, and I'm looking for the fastest way to do it with doing
> the least amount of damage.
> Is there any nuke button that I can press to kill this process with
> extreme prejudice? - at this point I don't care about the integrity of
> the table I was running the transaction on - I just want it to die.
> Is there any way to force the table to drop, thus killing the process?
>
> Is there any way to make a new log file for this database, and kill the
> log file that has the rolling back?
> If I stop SQL Server, will it try to wait until the transaction is
> done/rolledback before it will actually stop?
> Please HELP! Thanks in advance
> -Rob
>

HELP - need to kill big transaction that's taking too long to rollback

Hi all,
I have a big transaction running on a table that I had to kill and
rollback. Unfortunately, the transaction has been rolling back for 1.5
hours and is supposedly only 6% done rolling back. I need to stop this
transaction, and I'm looking for the fastest way to do it with doing
the least amount of damage.
Is there any nuke button that I can press to kill this process with
extreme prejudice? - at this point I don't care about the integrity of
the table I was running the transaction on - I just want it to die.
Is there any way to force the table to drop, thus killing the process?
Is there any way to make a new log file for this database, and kill the
log file that has the rolling back?
If I stop SQL Server, will it try to wait until the transaction is
done/rolledback before it will actually stop?
Please HELP! Thanks in advance
-RobStop the server service?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"robh1999atgmail" <RobH1999@.gmail.com> wrote in message
news:1159460802.483348.29370@.d34g2000cwd.googlegroups.com...
> Hi all,
> I have a big transaction running on a table that I had to kill and
> rollback. Unfortunately, the transaction has been rolling back for 1.5
> hours and is supposedly only 6% done rolling back. I need to stop this
> transaction, and I'm looking for the fastest way to do it with doing
> the least amount of damage.
> Is there any nuke button that I can press to kill this process with
> extreme prejudice? - at this point I don't care about the integrity of
> the table I was running the transaction on - I just want it to die.
> Is there any way to force the table to drop, thus killing the process?
>
> Is there any way to make a new log file for this database, and kill the
> log file that has the rolling back?
> If I stop SQL Server, will it try to wait until the transaction is
> done/rolledback before it will actually stop?
> Please HELP! Thanks in advance
> -Rob
>

HELP - ActiveX stuck in loop, cannot kill!

Someone please help--

I've been working on an ActiveX script in a DTS package. I executed the script and it's stuck in a while..wend loop. If I kill it I will lose all the code I wrote (pretty much a lot) since last saving the entire package.

Is it possible either:

a) Kill the activex step without killing the entire DTS designer session.
b) Locate the ActiveX code which must be in a temp table somewhere.

Please help I don't want to recode the entire object.

Thanks!If you kill the spid when eunning a query in qa it doesn't shut qa...

Now don't take my word for it, but maybe if you kill the spid, the designer session will still be open...

BUT WHY would you run something before saving and WHY would you have a loop of any kind?