An application that uses the KILL command to terminate a database connection

Question

Everything,

I decided that this would not happen, but often being one of several database administrators in my store, I like to hear about others.

We have a provider stating that they require membership in the processadmin member so that their application can kill for a long time or cancel user requests for their database. After 10 years, I had never encountered this as a requirement before. We currently have 400+ databases, and not one of them has users in the processadmin role. In my opinion, even if the user cancels this process in the application, the application code is responsible for elegantly opening and closing connections as necessary. If the request takes too much time, you must configure it.

Depending on what KILLed is, rollback can be quite burdensome and cause a lock. I would also like them to easily kill the wrong connection in a shared environment.
Does anyone else encounter such a situation? Anything obvious I'm missing?

Answer 1

If you rely on KILL to handle long queries that shouldn't take long, then T-SQL code definitely needs to be tuned. If this is a special SQL query sent to the engine from the on-the-fly query designer based on what users choose as their preferences on the application / web page web page, then the parameters provided to the user should be viewed, I’ll never was not a supporter of the killing of requests, until and until there was no other choice. In order to allow for production separation (as a workaround or an immediate solution), it may be acceptable at times, but not as practice.

Answer 2

I would not buy an application from such a provider, it should be poorly executed, poorly designed and buggy. Anyone who is not competent enough not to know that applications should not have administrator rights is not the one with whom I would buy the product.

Answer 3

While processadmin will get them what they need, you could create (or create on their behalf) a signed module that has the ability to kill certain processes (i.e. from your application). But even then I will resonate what everyone else is saying; this is not a good general practice.