 |
|
 |
|
Next: Modeling time intervals
|
| Author |
Message |
External

Since: Apr 17, 2008 Posts: 13
|
(Msg. 1) Posted: Thu Apr 17, 2008 1:29 am
Post subject: Incremental cube update with changing data in M2M dimension Archived from groups: microsoft>public>sqlserver>olap, others (more info?)
|
|
|
Hello,
I have a question about use of many-to-many dimensions. There is a
huge fact table joined to a dimension, and that dimension has a
factless many-to-many table with attributes attached. Question: when
attribues of a dimension record which has been used in the fact table
in the past change, do you have to re-compile the whole cube?
As an example, let's say you have a sales fact table and customers
dimension. There is a factless many-to-many table called
customer_parameters. At one point, one parameter changes for many
customers who've had sales in the past (for example, they change from
single to married). Do you have to re-compille the whole cube every
time such updates take place in a dimension? Is there a way to avoid
and/or delay that?
Thanks!
S. >> Stay informed about: Incremental cube update with changing data in M2M dimension |
|
| Back to top |
|
 |  |
External

Since: Jan 14, 2008 Posts: 69
|
(Msg. 2) Posted: Thu Apr 17, 2008 7:37 am
Post subject: Re: Incremental cube update with changing data in M2M dimension [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
you talk about a change in your factless table, this is NOT a change in the
dimension.
in this case you have to reprocess the factless table to make sure that the
customers parameters are correctly associated to the customers.
because you don't change the dimension himself, there is no need for a full
process of the sales.
Now... if your parameters dimension is directly attached to your sales fact
table (or referenced to the fact table), in this scenario you have to
reprocess your sales history. but with a many many, there is no need for a
process.
wrote in message
> Hello,
>
>
> I have a question about use of many-to-many dimensions. There is a
> huge fact table joined to a dimension, and that dimension has a
> factless many-to-many table with attributes attached. Question: when
> attribues of a dimension record which has been used in the fact table
> in the past change, do you have to re-compile the whole cube?
>
> As an example, let's say you have a sales fact table and customers
> dimension. There is a factless many-to-many table called
> customer_parameters. At one point, one parameter changes for many
> customers who've had sales in the past (for example, they change from
> single to married). Do you have to re-compille the whole cube every
> time such updates take place in a dimension? Is there a way to avoid
> and/or delay that?
>
>
> Thanks!
> S. >> Stay informed about: Incremental cube update with changing data in M2M dimension |
|
| Back to top |
|
 |  |
External

Since: Jan 29, 2008 Posts: 26
|
(Msg. 3) Posted: Sat Apr 19, 2008 12:55 am
Post subject: Re: Incremental cube update with changing data in M2M dimension [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Apr 17, 1:37 pm, "Jeje" wrote:
> you talk about a change in your factless table, this is NOT a change in the
> dimension.
> in this case you have to reprocess the factless table to make sure that the
> customers parameters are correctly associated to the customers.
>
> because you don't change the dimension himself, there is no need for a full
> process of the sales.
>
> Now... if your parameters dimension is directly attached to your sales fact
> table (or referenced to the fact table), in this scenario you have to
> reprocess your sales history. but with a many many, there is no need for a
> process.
>
> wrote in message
>
>
>
>
>
> > Hello,
>
> > I have a question about use of many-to-many dimensions. There is a
> > huge fact table joined to a dimension, and that dimension has a
> > factless many-to-many table with attributes attached. Question: when
> > attribues of a dimension record which has been used in the fact table
> > in the past change, do you have to re-compile the whole cube?
>
> > As an example, let's say you have a sales fact table and customers
> > dimension. There is a factless many-to-many table called
> > customer_parameters. At one point, one parameter changes for many
> > customers who've had sales in the past (for example, they change from
> > single to married). Do you have to re-compille the whole cube every
> > time such updates take place in a dimension? Is there a way to avoid
> > and/or delay that?
>
> > Thanks!
> > S.- Hide quoted text -
>
> - Show quoted text -
Jeje is right.
I've a concern about your model - when you say that that a parameter
changes for customers who've had sales in the past, are you sure you
want to "lose" the parameters for the past sales? You can also have
both, but depending on your requirement you could choose different
models.
I suggest you to take a look at my paper here: http://www.sqlbi.eu/manytomany.aspx
Look at the models "Transition Matrix" and "Cross-Time", you might
find some ideas for your models.
Marco Russo
http://www.sqlbi.eu
http://sqlblog.com/blogs/marco_russo >> Stay informed about: Incremental cube update with changing data in M2M dimension |
|
| Back to top |
|
 |  |
External

Since: Apr 17, 2008 Posts: 13
|
(Msg. 4) Posted: Mon Apr 21, 2008 1:10 am
Post subject: Re: Incremental cube update with changing data in M2M dimension [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Apr 19, 11:55 am, Marco Russo wrote:
> On Apr 17, 1:37 pm, "Jeje" wrote:
>
>
>
>
>
> > you talk about a change in your factless table, this is NOT a change in the
> > dimension.
> > in this case you have to reprocess the factless table to make sure that the
> > customers parameters are correctly associated to the customers.
>
> > because you don't change the dimension himself, there is no need for a full
> > process of the sales.
>
> > Now... if your parameters dimension is directly attached to your sales fact
> > table (or referenced to the fact table), in this scenario you have to
> > reprocess your sales history. but with a many many, there is no need for a
> > process.
>
> > wrote in message
>
> >
>
> > > Hello,
>
> > > I have a question about use of many-to-many dimensions. There is a
> > > huge fact table joined to a dimension, and that dimension has a
> > > factless many-to-many table with attributes attached. Question: when
> > > attribues of a dimension record which has been used in the fact table
> > > in the past change, do you have to re-compile the whole cube?
>
> > > As an example, let's say you have a sales fact table and customers
> > > dimension. There is a factless many-to-many table called
> > > customer_parameters. At one point, one parameter changes for many
> > > customers who've had sales in the past (for example, they change from
> > > single to married). Do you have to re-compille the whole cube every
> > > time such updates take place in a dimension? Is there a way to avoid
> > > and/or delay that?
>
> > > Thanks!
> > > S.- Hide quoted text -
>
> > - Show quoted text -
>
> Jeje is right.
> I've a concern about your model - when you say that that a parameter
> changes for customers who've had sales in the past, are you sure you
> want to "lose" the parameters for the past sales? You can also have
> both, but depending on your requirement you could choose different
> models.
> I suggest you to take a look at my paper here:http://www.sqlbi.eu/manytomany.aspx
> Look at the models "Transition Matrix" and "Cross-Time", you might
> find some ideas for your models.
>
> Marco Russohttp://www.sqlbi.euhttp://sqlblog.com/blogs/marco_russo- Hide quoted text -
>
> - Show quoted text -
Marco,
I've already downloaded you paper last week. It's great! At the mo,
our requirement is to use only the "current state", but once all that
is done will look into adding the "cross-time" scenario as well.
Most important was for me to make sure that re-compiling the M2M
dimension would not force us to recompile the main cube, as it is very
large.
Thanks!
Sergei. >> Stay informed about: Incremental cube update with changing data in M2M dimension |
|
| Back to top |
|
 |  |
| Related Topics: | How many fact tables allowed per cube? - Can an OLAP cube contain more than one fact table?
Storing natural keys in the dimension tables, to aid ETL m.. - I'm a beginner at DW and BI. I'm posting to this NG because my current (and first) data warehouse project is using SQL Server 2005 and my question is regarding the Kimball book "The Microsoft Data Warehouse Toolkit" (2006). The authors are say...
Slow Changing Fact Table / Snapshot - We have a small Contract tracking system that tracks 1 to many funding sources per 1 to many contractors per a given Contract. As the contract is making its way to completion - the funding sources can have many amendments. For example; a contract...
Updating data in a data warehouse - I found this thread about whether to update fact tables in data warehouses, other than for errors in the data. ..
Loading data - Hi I have following scenario table1 Columns X qty 1 20 2 30 table 2 cols X Y 1 A 1 B Now I should load data X Y qty 1 A ... |
|
You can post new topics in this forum You can reply to topics in this forum You can edit your posts in this forum You can delete your posts in this forum You can vote in polls in this forum
|
|
|
|
 |
|
|