>There also can be hybrid implementations if data preparation steps involved are too time consuming for total data pool. For instance a monthly time series analysis might
>calculate current partial monthly data
>read already calculated monthly pool data
>calculate time series data back from current start position - which might be needed every time, since drop of terminal value is not distributed even or current events will create different factors if trying to estimate base values of empirical data.
>
>You might consider this a "logical horizontal ETL table partitioning schema" if the updated data store is NOT partioned that way, only queries translate specific month ;-)

That is interesting. I remember when being involved in movies when we had this start position until we reached the end. It's like a restore point backup. I like this hybrid approach. I might have to use it one day.

Thanks