🚀 go-pugleaf

On a number of occasions in the past, I seem to have experienced rather strange
results after issuing the KILL command to cancel an errant process on MS SQL
Server for NT.  Server performance seemed to degrade significantly, and
otherwise inexplicable error messages appeared in the log, in the hours after
the KILLs were executed.

This has caused me to avoid using KILL altogether, and it has been long enough
since the last time I tried it that I have forgotten exactly what the error
messages were.  I remember that I noticed the performance degradation on at
least two occasions when, after I tried to KILL a process during the day,
overnight backups that normally run from 10 p.m. to about midnight were still
executing well into the next work day.  At the time we were running SQL Server
version 4.21 on NT 3.1; we have since upgraded to SQL Server 4.21a on NT 3.5; I
have not tried a KILL since the upgrade.

I apologize for the haphazard effort at problem documentation, but I was
wondering whether anyone else out there has experienced anything similar and,
perhaps, has been more diligent at determining the cause than I have been.  Any
opinions will be greatly appreciated.

Bob Christensen