on 12-29-2005 7:38 AM
Hello All
I have one navigational attribute and now Iam trying to create a aggregate for this attribute.after creating Aggregate for this now Iam trying to restrict to <b>FIXED VALUE</b> but its not accepting.How to restrict to <b>fixed value</b>.
Can anyone tell me how to do this?
And also what do u mean by <b>Flat aggregates</b>?
regards
balaji
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Balaji,
It seems impossible to make an aggregate on a navigational attribute without RSRT giving an error in RSRT that the char itself is missing and it cannot use the aggregate.
For more information click this link.
Thanks
Ramu
Hello Paolo
Case 1(according to u)
Let me know clearly like,for example if v have a characteristics(AC_Doc_No) and Doc_Name is one of the attribute of characteristics(AC_Doc_No).Now I made Doc_Name as a navigational attribute,Now if I create aggregate of characteristics(AC_Doc_No),then by default the Doc_Name is covered(as u said)is it the same way u r talking about.
Case 2(according to me)
What I want is I want to create 2 aggregates one for characteristics(AC_Doc_No) nd 2nd for Doc_Name(i.e Navigational attribute)
Can v do or not separetly.Pl let me know which case v can do.
regards
balaji
When a Nav Attr is referenced in a query, normally, the query that is generated includes a table join to the characteristic's master data table to get the nav attr value.
This incurs a join and read on another table. Depending on the size of the master data table and how it is read (full scan or indexed read) will determine the impact to the query's performance.
With an aggregate, this normally works the same way, however, if you are familiar with the queries that will use the aggregate and reference the navigational attribute, and are able to assess the performance impact, you can opt to actually embed the Nav Attr in the aggregate, just as if it was a characteristic.
That way, queries that use the aggregate, will not need to perform the join to the master data table. There are implications to the ongoing maintenance of the aggregate if you do this (Attribute Change Run) so it is something some wouldn't do without a good understanding of how aggregates work, how change runs work, and the ability to determine the impact to query performance of putting the Nav Attr in the aggregate.
Hi,
If you create an Aggregate with more than 16 characteristics, then we call that aggregate as FLAT Aggregate.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Naga
Thanks for your message.
U mean to say that One aggregate name like(AGGR_SAlES1) and under this 16 charactersitics.<b>Is it correct</b> orelse
16 Aggregates name(like AGGR_SALES1 to AGGR_SALES16)
And what is the <b>use</b> of this <b>Flat aggregates</b> and when shal v go for it.
regards
balaji
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.