A requirement for our warehouse is that we have validating and auditing on
every major step. The building of the cube being considered one of those
major steps.

Here's how we'd ultimately like it work:

1. Process cube and make the partition not queryable or visible for users
2. Check cube totals against fact table tables (stored procedure)
3. If the totals match up, make the partition available for querying. If
not, delete partitions

Think of this as commiting a transaction in SQL. We don't want to commit the
cube processing until the numbers have been verfied against the fact table
data.

Any ideas on how to go about tackling this?

WOW. Nothing in the system to do something like that.
One hack might be to remove all security on the cube so it becomes
un-queryable by the end user. Then have your application bind to the cube as
an OLAP administator (which always has access to the data). Obviously your
app could then establish rhe right roles when it is done.

Being able to "unprocess" a partition is a new feature in 2005. The only way
I know to do this in SQL2K is to monkey around with the partition folder.
But this is high risk and I don't advise it. Remember that in SQL2K, the
actual runtime engine doesn't use the repository at all. It relys excusively
on the folder structure. Therefore you need to reset some files if you want
the partition data to disappear. Good luck trying to do with SQL2K -- but
very easy with 2005.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Jesse O" <jesperzz (AT) hotmail (DOT) com> wrote

Again, thanks for the reply Dave.


"Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> wrote