Downgrade to SQL Monitor 2.3
gsmith151
Posts: 5
I recently upgraded from version 2.3 to version 3.1 after attending SQL in the City as wanted to take advantage of custom metrics functionality.
However, since I upgraded to 3.1 the long-running query does not return the SQL fragment information any longer. Apparently this is a bug for version 3; so now I would like to go back to version 2.3 until this is fixed in next release, however, support are telling me they wouldn't advise downgrade as unsure what will happen to the repository if I do so.
Anybody got any ideas or experience of having to do this due to bugs in version 3??
Thanks,
Gavin
However, since I upgraded to 3.1 the long-running query does not return the SQL fragment information any longer. Apparently this is a bug for version 3; so now I would like to go back to version 2.3 until this is fixed in next release, however, support are telling me they wouldn't advise downgrade as unsure what will happen to the repository if I do so.
Anybody got any ideas or experience of having to do this due to bugs in version 3??
Thanks,
Gavin
Comments
Version 3.2 should be available in just over a weeks time, so this may be a lot of work for only 7-14 days of benefit.
I've managed to downgrade to version 3.0 and it seems to be working OK so far so I'll stick with this version for the time being.
Thanks for the reply!
http://www.red-gate.com/sqlmonitor
This fixes the LRQ alert bug.
Regards
Chris
Test Engineer
Red Gate