That said, the fix for this particular problem is quite easy, thanks to SQLCLR integration! The .NET Framework BCL contains a namespace called System.Diagnostics, which has a class called Process. The Process class exposes a method called Kill. I'll leave it as an exercise for the reader to roll this method into a SQLCLR routine that can be used to terminate a process -- just like the undocumented extended stored procedure.
Dig Deeper on Microsoft SQL Server 2005
Related Q&A from Adam Machanic
Migrating to SQL Server 2005 from SQL Server 2000 is a hefty feat when compared to upgrading from 7.0 to SQL Server 2000. Site expert Adam Machanic ... Continue Reading
Multiple readers can sometimes read the same row simultaneously causing a false result. SQL Server 2005 expert Adam Machanic suggests modifying the ... Continue Reading
SQL Server 2005 and T-SQL do have differences. The advantages and disadvantages would depend user environment as described by SQL Server 2005 expert... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.