Re: Cannot process partition, Analysis Mgr. freezes

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: adami (adami_at_discussions.microsoft.com)
Date: 11/30/04 

Date: Tue, 30 Nov 2004 15:17:02 -0800

That was it, optimizing the schema.
I'll have to schedule that from now on.
Thanks,
ADAM

"Dave Wickert [MSFT]" wrote:

> I hoped you have followed the suggestions as outlined in the SSAS Operations
> Guide.
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/anservog.mspx
>
> One of the best practice is to turn on the system-wide processing log file.
> If you have done that, you can go back into history and see if the SQL
> statements have changed. My guess is that that is what has happened. That
> the SQL statements have changed over time.
>
> For example, you might have removed then added a dimension. When the new
> dimension comes into a cube it is unoptimized. At one point in time, you
> might have ran the Optimize Schema tool (in the cube editor), which can
> greatly simplify the complexity of the SQL Statement, but over time all of
> the dimension activity might have undone the optimization and you have a
> large number of joins being issued to the data source.
>
> --
> Dave Wickert [MSFT]
> dwickert@online.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.
>
> "adami" <adami@discussions.microsoft.com> wrote in message
> news:83D3EE56-E7DF-4DBD-81B5-42CB1CD28AA3@microsoft.com...
> >
> > I have 1 cube with many partitions (1 per day for 5 months). The
> dimensions
> > process fine, but when I add a new partition, slice it, then process it,
> > Analysis Mgr. becomes unresponsive.
> > It worked fine for 5 months with no degredation in performance or
> processing
> > speed (usually 15-20 min per day), then just started this problem out of
> > nowhere.
> >
> > The fact table about 1 billion rows, and is partitioned by day and is an
> > Oracle db.
> >
> > The same thing happens when processing in code, it just stops once I've
> > started processing the partition.
> >
> > I have the latest of everything (SP3a), latest MDAC.
> > Any ideas?
> > Thanks,
> > ADAM
>
>
>

Relevant Pages

  • Re: Drillthrough problem
    ... Is "bananas" a technical term? ... is caused by the fact that an unoptimized schema has an inner join with the ... dimension table and -- as we all know -- inner joins eliminate data with no ... non-existent dimension members, then in the processing of an unoptimized ...
    (microsoft.public.sqlserver.olap)
  • Re: Cannot process partition, Analysis Mgr. freezes
    ... the SQL statements have changed over time. ... you might have removed then added a dimension. ... SQL BI Product Unit (Analysis Services) ... > started processing the partition. ...
    (microsoft.public.sqlserver.olap)
  • Re: OLAP cube - invalid join between fact table and dim table
    ... If you look at the SQL statement, the default for an unoptimized schema is ... means that missing dimension rows just "disappear" before AS even gets them. ... If you optimized the schema (using the Optimize Schema tool in the Cube ...
    (microsoft.public.sqlserver.olap)
  • Re: A silly question ... just to clarify my concepts
    ... in SQL" ... Use a nested sets model for the dimension tables in your data mart. ... You clearly did no research before writing your schema, ...
    (microsoft.public.sqlserver.programming)
  • Re: Relational-to-OOP Tax
    ... In what way would that affect the other old applications? ... Coupling the application to the schema makes ... existing SQL statements will break if you add columns or tables. ... and schemas change for different reasons has been demonstrated. ...
    (comp.object)