Can't Kill Process

We unfortunately found out that our databases were not being backed up for 9
5
days on one of our servers because the backup job got "stuck" on one of the
databases. I don't know why. I stopped the job but now the backups will not
work because the backup job from May is still "in process" on that one
database.
I tried killing the process but it won't work because there is "a rollback
in process". I rebooted the server but that did not help.
Does anyone have any suggestions on how I can kill this process on this one
database?
Thanks,
David McCarterFYI -
A rollback takes AT LEAST the same amount of time as it did to perform
whatever operations a transaction was doing. So, if a process has been
running for 1 hour and you decide to roll it back, then it would take at
least another hour to undo whatever it had already done.
"dotNetDave" <dotNetDave@.discussions.microsoft.com> wrote in message
news:27D4013A-7E4E-493A-A56E-EA9AD1D1CF27@.microsoft.com...
> We unfortunately found out that our databases were not being backed up for
> 95
> days on one of our servers because the backup job got "stuck" on one of
> the
> databases. I don't know why. I stopped the job but now the backups will
> not
> work because the backup job from May is still "in process" on that one
> database.
> I tried killing the process but it won't work because there is "a
> rollback
> in process". I rebooted the server but that did not help.
> Does anyone have any suggestions on how I can kill this process on this
> one
> database?
> Thanks,
> David McCarter|||So are you saying the rollback is going to take 95 days? That's how long
the process was running before someone noticed it.
"The DBA" wrote:

> FYI -
> A rollback takes AT LEAST the same amount of time as it did to perform
> whatever operations a transaction was doing. So, if a process has been
> running for 1 hour and you decide to roll it back, then it would take at
> least another hour to undo whatever it had already done.
> "dotNetDave" <dotNetDave@.discussions.microsoft.com> wrote in message
> news:27D4013A-7E4E-493A-A56E-EA9AD1D1CF27@.microsoft.com...
>