Timeline for How to identify a Windows Remote Desktop user by SQL Server session id?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 23, 2019 at 13:27 | vote | accept | MicSim | ||
| Jun 3, 2019 at 15:48 | comment | added | MicSim | @Peter Vandivier: I'm not going to blame the user, but want to know, what they did, so the blocking took place. The blocking in this special case is an absolute exception. So I could have killed the query and go on (which in effect I did, after being unable to identify the user). | |
| Jun 3, 2019 at 15:45 | comment | added | MicSim | @Tony Hinkle: Yes, the SQL login is being shared by other users. | |
| Jun 3, 2019 at 15:01 | comment | added | Peter Vandivier | There's a couple ways to go with this question. But "blaming" a user for running a blocking query is probably coming at the problem from the wrong end of the ice-cream cone. Any reason you can't just kill blocking queries as-and-when you need to? | |
| Jun 3, 2019 at 15:01 | answer | added | George.Palacios | timeline score: 2 | |
| Jun 3, 2019 at 14:54 | comment | added | Tony Hinkle | So--is the SQL login that the user is using being shared by other users? | |
| Jun 3, 2019 at 14:33 | history | asked | MicSim | CC BY-SA 4.0 |