Long-running query SQL process fragment Unknown
fifthrace
Posts: 15
Since upgrading to 3.1, I've noticed that on the Long-running query alert my SQL process fragment is no longer showing as it did before in the UI.
I apologize if I missed something that stated why this would be. Any help would be much appreciated.
Thanks all,
Robbie
I apologize if I missed something that stated why this would be. Any help would be much appreciated.
Thanks all,
Robbie
Comments
A bug has been raised (ref: SRP-6952) and we'll be looking to fix this for the next release.
Regards
Chris
Test Engineer
Red Gate
I hope this bug has been given a high level of priorty because the LRQ (long Running Query) alert is just about useless without this key piece of information.
I'm suprised that this is not being fixed till the next release of SQL Monitor. Then again maybe no other user besides myself makes use of the LRQ alert and so this is not a major setback/bug for anyone else.
Thanks
Downgrading to 3.0 would get the SQL Fragment info back but I'm not sure if the v3.0 software would work with a v3.1 data repository. I'd have to test that.
Regards
Chris
Test Engineer
Red Gate
FYI - So far the downgrade is working. I have yet to have any probelms or errors and most importanty, I got back my missing SQL Fragment info for LRQ alerts.
I was worried that the info had been permanently lost and not just missing but its still there. I just wish I knew how to get that info directly from the DB.
Thanks
Regarding getting the information out of the repository, I've had a little go at doing this and come up with:
I think that this at least maps SQL fragments to Process IDs.
Regards
Chris
Test Engineer
Red Gate
I think that this is a fairly safe estimate but if it changes I'll post an update.
Regards
Chris
Test Engineer
Red Gate
http://www.red-gate.com/sqlmonitor
This release fixes the LRQ alert issue.
Regards
Chris
Test Engineer
Red Gate