Ability to store a baseline
After attending SQL in the city and listening to Grant Fritchey talk about the need to create baselines (and demo sql monitor) a feature I would like is the ability to create a baseline over 24 hours and have it stored. This could be then added to the analysis page as a Versus. ie last hour vs baseline, last day vs baseline.
With SQL Monitor v.3.5 introducing a powerful baselining feature, we consider this suggestion as completed.
One thing our implementation doesn’t do (though it was mentioned in a couple of comments) is to be able to “freeze” a data range so as to retain a static baseline. We’ve created a suggestion for this additional functionality – so if you are interested in that aspect please vote on the following suggestion: http://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/11122092-select-and-store-a-static-baseline-for-future-refe
Ray Herring commented
It would be nice to have rolled up or aggregated metrics for the baseline. For example, when the data is older than a week aggregate Hourly Min, Max, Avg Disk Sec/Read. When the data is older than a month aggregate Daily min, max, avg with high hour, low hour.
Also provide a way to designate a particular interval as a baseline. Like a snapshot. I would like to have perhaps a half dozen different snap shots for the instance and for each DB. These would be "permanent" and retained until the user replaced or deleted them.
Daniel, this request is wholly different from the baselines available in SQL Monitor v3.5. We need to be able to store a baseline for performance for a given duration, in isolation, for as long as we choose. Not to have to keep everything from a point in time in order to draw baselines from that data. this request should not be closed.
Thanks for your feedback and suggestion Blaz.
Blaž Dakskobler commented
First, props for the feature. Was already using the compare feature extensively, this is a nice upgrade to that.
I'd like to point out something that came to my mind while using it - sometimes you get data you would like to exclude from the baseline. Let's say you want to check out some graph for today, 24 hours back and extend that a couple days more into the past. The problem is what if one day was completely off the baseline - you'd want to exclude that, else it skews the baseline.
Don't really have an idea how to solve this elegantly, but thought I'd share this with you anyway.
Thanks for your feedback.
We are currently discussing baseline and in the process of scoping it. But I am afraid we dont have any dates yet. Will update this thread as soon as we have some dates.
Jiri Berente commented
A great idea. When it will be implemented?
John Stafford commented
Definitely a useful idea - could we store several / a few baselines?
I was also at Grant's talk at SQL in the City and remember he did emphasise the importance of baslines. We really like the idea of saving a baseline for comparison and we'll post back when we have an update on this.
Thanks both for the feedback
Thanks a lot Andrew and Kevan for your feedback. This is great idea.
excellent idea. Maybe also add baseline management, so that after a major change you can 'recalibrate' your baseline