Re: Several Partitions vs Several Cubes

Absolutely agree. Use partitioning.

There is a discussion of partitioning in the SQL Server 2000 Resource Kit
book, and here:
http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/part6/c2661.mspx
(in the section titled Partition Strategy)

And here: (AS Performance Guide)
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ansvcspg.mspx
(all over the place)

And here: (AS Operations Guide)
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/anservog.mspx
in the section titled: Performance Configuration Issues (among other
sections)
--
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.


"Jéjé" <willgart_A_@xxxxxxxxxxxxxx> wrote in message
news:Op7NnMlgFHA.2472@xxxxxxxxxxxxxxxxxxxxxxx
>I recommand parititions!
>
> the work required to "merge" these cubes into 1 virtual cube and create
> calculated measures which aggregate the 450 measures of the 450 cubes is
> big.
>
> also, with cubes you have 450 cubes to manage. 1 change = 450 changes !!!
>
> also, with a virtual cube in top of your cubes, you can have a problem if
> 1 or more cubes is not processed.
> For example, if you change 1 dimension (or you do a full process of 1
> dimension), then you have to reprocess all cubes before the virtual cube
> can be used. With the partition option you must reprocess all partitions,
> but after the creation of the first partition, the cube is accessible to
> the end user. (Well only 1 district accessible at this time, but its
> better then nothing)
>
> in another way, if you have no plan or no measure across these 450
> districts ("all districts" not available and no district comparison
> needed) then you can have 450 cubes whitout any virtual cube and each user
> must select the cube to use.
>
>
> "Tim Chapla" <tchapla@xxxxxxxxxxxxxxxxxxx> wrote in message
> news:OlxB8ElgFHA.1148@xxxxxxxxxxxxxxxxxxxxxxx
>>I am looking for someone who can give some advice on creating
>>partitions/cubes.
>>
>> Here is my situation:
>> I have a fact table with 80 million rows (results for kids in a state).
>> I create a giant cube with all the results and it takes too long to
>> process. (I have the need to process this data a couple times a day)
>>
>> I am researching creating several cubes (450, one per district)
>> VS
>> creating several partitions (450, one per district) for the same cube.
>>
>> It is my understanding that I can process partitions separate from one
>> another which would allow me to do more of a selective update on the
>> cube.
>>
>> Anyone out there have any advice or resources they could point me to
>> which would assist me in making this decision?
>>
>> tx,
>> tim
>>
>
>


.

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: Validating a cube prcoessing job
    ... thanks for the reply Dave. ... Then have your application bind to the cube ... > Being able to "unprocess" a partition is a new feature in 2005. ... >> Think of this as commiting a transaction in SQL. ...
    (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: Why does my virtual cube always get processed (OLAP 2000)
    ... Thank you for your reply and I understand you do not want to virtual cube ... Partition 'Sales' (segment 1) ...
    (microsoft.public.sqlserver.olap)