Timeline for What is this query, involving system views & index properties
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 22, 2017 at 15:37 | vote | accept | NateJ | ||
| Jun 22, 2017 at 15:36 | answer | added | NateJ | timeline score: 1 | |
| Jun 22, 2017 at 15:36 | answer | added | John Eisbrener | timeline score: 1 | |
| Jun 22, 2017 at 14:50 | comment | added | NateJ | Using @JohnEisbrener's suggestion, I got the user/DB/program/machine-name, and it's NOT a recognized monitoring tool. It's an internal process of some kind (whether it's homegrown or just a local implementation of a monitoring-tool-look-alike remains to be seen). | |
| Jun 6, 2017 at 19:38 | comment | added | Tony Hinkle | If it's running that often, run a trace for a few minutes and you should be able to find it and see the client application name... | |
| Jun 6, 2017 at 16:21 | comment | added | John Eisbrener | How did you capture the plan? Did you capture the connection information as well? If not, get that and start looking into the client-side server/IP. Hopefully you identify that it's a monitoring solution, application, or something else non-alarming. | |
| Jun 6, 2017 at 15:52 | comment | added | Brent Ozar | If you're using a monitoring tool, that's probably where I'd start with a support call. It looks like a monitoring tool. | |
| Jun 6, 2017 at 15:44 | history | asked | NateJ | CC BY-SA 3.0 |