Hi,

I'm using a lot of attribute to order a displayed attribute
currently I setup this attribute to not optimized and
attributehierarchyenable is set to false.
and finally the relationship is set to rigid between the attribute and the
"order attribute"

does it the correct setup?
or I have to set the option to fully optimized for this attribute too?

thanks.

Jerome.

The related properties are AttributeHierarchyOrdered, OrderBy and
OrderByAttribute.

Below is from BOL.

--
The AttributeHierarchyOrdered property determines whether the members of the
attribute are ordered. The OrderBy property on the attribute determines how
the attribute is ordered. Specify Key to order by the key column specified
by the KeyColumn property, or specify Name to order by the name column
specified by the NameColumn property. To order by the key column or name
column on a related attribute, specify AttributeKey or AttributeName, and
then use the OrderByAttribute to specify the attribute. The OrderByAttribute
list includes attributes that are member properties of the attribute.
--

FYI, if AttributeHierarchyEnable is set to false, the releated attribute
does not appear as a hierarchy.
The attribute can do role of only member property.

Ohjoo



"Jeje" <willgart (AT) hotmail (DOT) com> wrote

sorry maybe my question is not clear.
my attributes are correctly setup and correctly ordered.

my question is about the configuration of the "order" attribute.
if this attribute is not fullyoptimized, does this impact the performance?
how these attribute should be setup?

"Ohjoo Kwon" <ojkwon (AT) olap (DOT) co.kr> wrote