Sorry, for whatever reason I don't have permission on this repo to call it an enhancement, which is what it is. The DREBS snapshot strategy has really served Inspire Commerce well, however there are aspects of it that make long term retention challenging... primarily thinning history (because Sh$t gets expensive). For example, I have 663 snapshots of our DB since August 2014... FOR 2014. 2015 is another 1100 as of this post. That's a LOT of data. What would be awesome, is to say, "after 5 days, thin records to only the snapshot at midnight (in stead of every hour), and after 60 days, thin records to only what was the record on the last day of the month at midnight. Ok, so this might not be the logic you build, but it would be REALLY useful about now to have something like this. Whatever the strategy is, I'd love to see whatever becomes of drebs address this "thinning" necessity over time that we face... otherwised were left with blunt instruments like dump everything older than x... and that isn't very good for our requirements.
Sorry, for whatever reason I don't have permission on this repo to call it an enhancement, which is what it is. The DREBS snapshot strategy has really served Inspire Commerce well, however there are aspects of it that make long term retention challenging... primarily thinning history (because Sh$t gets expensive). For example, I have 663 snapshots of our DB since August 2014... FOR 2014. 2015 is another 1100 as of this post. That's a LOT of data. What would be awesome, is to say, "after 5 days, thin records to only the snapshot at midnight (in stead of every hour), and after 60 days, thin records to only what was the record on the last day of the month at midnight. Ok, so this might not be the logic you build, but it would be REALLY useful about now to have something like this. Whatever the strategy is, I'd love to see whatever becomes of drebs address this "thinning" necessity over time that we face... otherwised were left with blunt instruments like dump everything older than x... and that isn't very good for our requirements.