Yes, Tim was able to convey what I was thinking about Essbase not being a OLTP.. the concept of transactions and rollback don't exist.
I feel that this might be possible, but you'd need deep knowledge of the tool and an extensive amount of work to pull off what a relational database can do with just a few simple commands. Of course Essbase can do a lot of things that relational tools can't do too.
I like Alan's suggestion; using hierarchies to preview the affect of a change, then if approved, calc (or load) the change into a permanent intersection (or something along those lines). So many options, IMO, that's why you need to really know Essbase to know which route is the best for this particular problem.
Scoring disabled. You must be logged in to score posts.