Re: "see this technique applied to an accumulating snapshot fact table"

Actually the technique is likely most appropriate for a transaction fact table of the type discussed in the article. By definition an accumulating snapshot fact table has a fixed number of dated buckets into which its facts are recorded. This type of fact table is a natural fit for workflow type situations where there are designated points in the workflow that we're interested in. A transaction fact table, on the other hand, is by definition atomic. The bulk of the transactions are likely never adjusted so even one additional set of attributes to accomodate an adjustment will be sparse. Furthermore one must look up the original fact in an accumulating fact table and update the row. An expensive operation when compared to an insert. The point of throwing the count off is well taken but I think the alternatives given accomodate that difficulty quite well. Nice article. Thanks