Re: Validating a cube prcoessing job

Again, thanks for the reply Dave.


"Dave Wickert [MSFT]" <dwickert@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:u72SdUulFHA.3316@xxxxxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxxxxxxx
> 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@xxxxxxxxxxx> wrote in message
> news:ek0Xb18kFHA.708@xxxxxxxxxxxxxxxxxxxxxxx
>>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?
>>
>
>


.

Relevant Pages

  • Analysis Server Incremental Update on Changing Dimensions
    ... Error during lazy aggregation of partition ... Broadcast_Response_2004_07 in cube Broadcast_Response: ... Microsoft Gold Certified Partner for Business Intelligence ...
    (microsoft.public.sqlserver.olap)
  • Re: Analysis Server Incremental Update on Changing Dimensions
    ... Error during lazy aggregation of partition ... Broadcast_Response_2004_07 in cube Broadcast_Response: ... incrementally update our changing Dimensions everyday. ...
    (microsoft.public.sqlserver.olap)
  • Re: Several Partitions vs Several Cubes
    ... > the work required to "merge" these cubes into 1 virtual cube and create ... With the partition option you must reprocess all partitions, ... > districts ("all districts" not available and no district comparison ...
    (microsoft.public.sqlserver.olap)
  • Re: DSO ERROR
    ... But another question," multi-user concurrently process different partition ... With regards to whether or not two users can be processing the same cube; ... >> Program Manager ...
    (microsoft.public.sqlserver.olap)
  • Re: Validating a cube prcoessing job
    ... One hack might be to remove all security on the cube so it becomes ... I know to do this in SQL2K is to monkey around with the partition folder. ... > Think of this as commiting a transaction in SQL. ...
    (microsoft.public.sqlserver.olap)