If you are unable to get the process to respond to the KILL command, the only alternative is to stop and restart the sqlserver service. I'm unaware of Microsoft planning to ever resolve this type of issue. The only resolution would be to have a "forced" kill, but such a command would open up opportunities for database corruption.
> This is not a large rollback, though. This is killing the query analyzer or
> enterprise manager application in the middle of a long select or something.
> > Geoff,
> > With large rollbacks, if you don't want to stop SQL Server, you have to
> > for them to finish. When you stop the service, you can delete the
> > transaction log, SQL Server will declare the database suspect, you can
> > delete it and then restore from a backup.
> > But otherwise, SQL Server will not work with databases that have
> > inconsistent data, and until the rollback is finished, the database is in
> > inconsistent state.
> > HTH,
> > Ron
> > --
> > Ron Talmage
> > SQL Server MVP
> > > We indavertantly closed enterprise manager while it was running a query
> > and
> > > now we can't get rid of that process. It continues to show rolling back.
> > > This was an issue in 6.5 and 7.0 when you closed query analyzer in the
> > > middle of a query. Besides stopping the service is there anything we can
> > do
> > > to stop/kill this process? Kill obviously doesn't work.
> > > Geoff