ALTER TABLE WITH SLIDE WINDOW
Sliding window scenarios are very common with partitioned tables, however the administration of these is too complex.
Upvotes: 4<=-=Oct 12 2010 9:43AM=-=>
Thanks for contacting Microsoft SQL Server team and your suggestion. Wondering if you can elaborate on the specific issues and how your proposal will address those?
With this one, it’s just the number of commands, etc. required to achieve the result. Building a sliding window seems to be the most common use of partitioning yet using partitioning in this way is quite messy.<=-=May 17 2011 12:51PM=-=>
Thanks for your explanation. We are currently keeping it in our list of features to reconsider as part of our next release planning.
Microsoft SQL Server Engine Team
Could you please give us some more details about what exactly you are looking for and what kind of an experience is desired? We need more elaboration on specific issues and what kind of a solution you expect, before we can proceed.
I find that the most common scenario that people implement using partitioned tables is some form of sliding window. Particularly common is the scheme where a range of dates is held in each partition. But many admins are quite overwhelmed by the steps that are needed at the end of each period to achieve:
1. The oldest period of data switched out
2. A new empty period created
3. All associated changes needed to the partition function & scheme
I just think that there should be a way of making this trivial. It might not be a DDL change. Even though I love to see most of these things as DDL, this might just be a set of system stored procedures that helps turn these operations into a single step.
Eitan Blumin commented
Oracle had something akin to automatic sliding windows for quite a while now. Just saying.