RESTRUCTING in EssBaSE
RESTRUCTING:-
Analytic services performs restructuring when ever there to be existing outline. There are 3types of resstructing.
OUTLINE-ONLY RESTRUCTURE:-
if a change affects only the database outline, analytic services does not restructure the index or data files. Member name changes creations of aliases , and dynamic calculation formula changes are examples of effects only the database outline
SPARSE RESRUCTURE:-
if a member of sparse dimension or a member of an attribute dimension is moved, deleted, or added , analytic services are restructures the index and is relatively fast ; the amount of time required depends on the size of the index
FULL RESTRUCTURE :-
if a member of console dimension is moved deleted, or added , analytic services are restructures block in the data files and create new data files when analytic services restructures the data blocks . it regenerates the index automatically so that index entries point to the new data blocks . analytic services marks all restricted block as dirty , so after a full restructure is the most time consuming of the restructure and for large databases can take a very long time to complete .
FULL RESTRUCTURE
To perform a full restructure , analytic services does the following :
- Creates temporary files that are copies of the .ind, .pag, .esm , and .tct files . each temporary file substitutes either N or U for the lost character of the files Extension , so the temporary file names are dbname.inn, essxxxxx.inn, essxxxxx.pan, dbname.otn, dbname.esn, dbname.tcu.
- Reads the block from the database files copied in step 1, restructures the block in memory, and then in new temporary files . this step takes the most time
- Removes the database files copied in step 1, including .ind, .pag, .esm, and .tct files.
- Renames the temporary files to the correct file names: .ind, .pag, .esm, and .tct
@CHILDREN
Returns all children of specified member , excluding the specified member . @ children (mbrname)
CHILDREN(QTR1) returns jan, feb mar. @CHILDREN returns jan, feb, mar and QTR1 also
@DESCENDANTS
Return all descendants of the specified member . @descendants(year) will return all members under year
ANCESTORS(QTR4) returns year .
@SIBLINGS
Returns all siblings of the specified member . @ siblings(qtr1) returns qtr2,qtr3,qtr4. Siblings (qtr1) returns qtr1,qtr2,qtr3and qtr4.
@RSIBLINGS
Returns the right siblings of the specified member. The members next to it . @RSIBLINGS(QTR2) returns qtr3, qtr4.
@LSIBLINGS:
Returns the left siblings of the specified member . the member above it @LSIBLINGS(qtr2)
Returns qtr1.
@MATCH:-
Performs wildcard member selections .
@match (time , “j*”) returns all the months that are starting with : JAN,JUN, AND JUL
@PRIOR:-
Returns the nth previous cell member from mbr name range list
“OPENING INVENTORY @PRIOR (ENDING INVENTORY)”
@CONCATENATE:-
Returns a character string that is result of appending one character string to another character string
SYNTAX:-
@CONCATENATE(STRING1, STRING2)
@UDA
Returns member based on a common attribute , which you have defined as a user- defined attribute (UDA) on the analytic server.
SYNTAX
@UDA (DIMNAME, UDA)
@UDA (GEOGRAPHY, SMALL)
@ATTRIBUTE
Lists all base members that are associated with the specified attribute member (attmbrname)
@ATTRIBUTE(1L) returns all the members in product dimension whose attribute is 1L
@ RELATIVE
Returns all members at the specified generation or level that are above or below the specified member in the database outline .
SYNTAX
@RELATIVE(mbrname, genlevnum 1 , genlevname)
Examples are discussed in the class,
@ISCHILD
Returns TRUE if the current member is a child of the specified member . this function excludes the specified member .
SYNTAX:-
@ISCHILD(mbrName)
@WITHATTR
Returns database members that are associated with an attribute that satisfies the conditions you specify. You can use operator such as >, <. =, and IN to specify conditions that must me.
@ATTRIBUTE(Bottle)
@WITHATTR (EXG Type “,”==”.Bottle)
However, the following formula can be performed only with @WITHATTR(not with @ ATTRIBUTE) because you specify a condition.
@WITHATTR(Ounces,”>”, “16”)