Re: lazy aggregates

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

From: PCH (pch12_at_hotmail.com)
Date: 03/30/04

  • Next message: Brian Altmann: "RE: Period.Currentmember.name" 
    Date: Tue, 30 Mar 2004 09:41:16 -0800

    So if I can't move it until the lazy aggs are done, I might as well use
    standard agg processing and when the DSO object completes, its ready to
    copy. Sound right?

    "Dave Wickert [MSFT]" <dwickert@online.microsoft.com> wrote in message
    news:e6NvEUeFEHA.1272@TK2MSFTNGP12.phx.gbl...
    > This is covered in the AS Operations Guide and the Performance Guide.
    > Pointers at:
    >
    http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/anservog.mspx
    >
    http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ansvcspg.mspx
    >
    > But to answer your specific questions:
    > 1) Don't move the data while processing is occuring. You will have
    > inconsistent results. There is a script in the Operations Guide that will
    > help you determine when lazy processing is done.
    > 2) Lazy aggregates are calculated on a background thread. It is very CPU
    > intensive (as you would expect), so you will see all of your CPUs pegged
    > while background processing is occurring. Queries are handled on normal
    > priority threads and are not affected.
    > --
    > Dave Wickert [MS]
    > dwickert@online.microsoft.com
    > Program Manager
    > BI Practices Team
    > SQL BI Product Unit (Analysis Services)
    > --
    > This posting is provided "AS IS" with no warranties, and confers no
    rights.
    >
    >
    > "PCH" <pch12@hotmail.com> wrote in message
    > news:u%23Z4NzbFEHA.3424@tk2msftngp13.phx.gbl...
    > > If my cube is setup for lazy aggregations, and I process it on a Staging
    > > server, and then immediately after processing I copy the data to the
    > > production server, will that production server still build the indexes
    and
    > > aggregations in the lazy fashion?
    > >
    > > Are the aggregations built based on idle time only, or on what the
    queries
    > > are returning?
    > >
    > > Thanks.
    > >
    > >
    >
    >

  • Next message: Brian Altmann: "RE: Period.Currentmember.name"