I've a request from management, but it raises flags for me, so I'm curious if I'm right or wrong about it.
From our VB.net Windows code, some searches may take a long time to run, given certain params that users may customly create. What management wants is "after clicking a search, add a pop-up with a Cancel button to allow users to cancel the operation if they feel it's taking too long." (And yes, we optimize where we can, so moving on...)
First, after I execute a proc or query command from VB.net to the SQL DB, how then can I tell SQL Server to stop it?
And second, if I can do this, is it a potential problem? It seems that enabling excessive "kill" commands (or whatever it may be called) to our users in a multi-user environment isn't the wisest thing to do, but maybe I'm wrong. Thoughts?