forum

Home / DeveloperSection / Forums / Application using KILL command to terminate DB Connection

Application using KILL command to terminate DB Connection

Anonymous User137419-Jun-2015

I have made up my mind that this is not going to happen, but often being one of just a couple of DBAs in my shop I like to hear the experiences of others.

We have a vendor stating they require processadmin role membership so their app can KILL long running or user cancelled queries against their DB. In 10+ years I have never ran into this as a requirement before. We currently house 400+ databases and none have users in the processadmin role. In my mind, even if the user cancels a given process within the app, the application code is responsible for gracefully opening and closing the connections as needed. If a query is taking "too long" it needs to be tuned.


Depending on what is being KILLed, rollback could be quite burdensome and cause blocking. I would also be concerned they could easily kill the wrong connection in a shared environment.

Anyone else run into a situation like this? Anything obvious I am missing?


Updated on 19-Jun-2015
I am a content writter !

Can you answer this question?


Answer

1 Answers

Liked By