A bit like Dr Who, SQL Response 2 will allow you to “rewind time” back to a specific point – for example 2 minutes ago, last Wednesday, six weeks, or even six months earlier – to see overview data for a server or SQL Server instance exactly as it was at that point in time.
This will allow you to compare what’s going on at certain times of the day or days of the week, or inspect the status of the system when a specific issue occurred in the past. It will also enable you to look at trends for a whole range of metrics over different timescales.
However, we’d like to know how far back, realistically, you need to go to look at this kind of data. Do you consider a month to be sufficient? Two months? A year? Longer?
And what kind of data do you or would you particularly look for when travelling back in time in this way? Would you expect an alert from six months ago to still be able to display all metric data from the period when it was raised (such as CPU% or scans/sec) as part of its diagnostic data? What about the case of overviews – ie not tied to a specific alert – would you want to see all metric data and info about databases, jobs,indexes etc from six months ago?
Any policy for storing historical data is very much dependent on how much disk space you have available. How much disk space do you feel is realistic or viable for the SQL Response database to require? Is disk space an issue for you at all?
We’d love to hear your views, so we can figure out how best to handle historical data, based on realistic use cases. Tell us what you do currently, and what you’d like to do, in an ideal world. Thanks for reading!