MDX querry

Hello
I'm new in MDX and faced the following problem

WITH
MEMBERS [year]. [Semi-annual] AS ' ([Qtr1] + [Qtr1])'
MEMBER [Measures]. [%] AS ' ([Total Expenses] / [Margin] * 100)'

SELECT {[T1], [Qtr2], [semi-annual]} ON the RANKS.
{[Margin], [Total cost], [percentage]} ON COLUMNS
[EXAMPLE]. [Base]

I don't know how to count first-half percentage correctly (now its bigger than 100%) because on the one hand, half a year is equal Qtr1 and Qtr2 but in the case of percent, it should be equal total cost/margin
Any suggestion would be appreciated!


Concerning
Sasha

You may need to add a solve order because it is add the percentages of Qtr1 and Qtr2.

Try

WITH
MEMBERS [year]. [Semi-annual] AS ' ([T1] + [Qtr2])', SOLVE_ORDER = 1
MEMBER [Measures]. [%] AS ' ([Total cost] / [Margin] * 100)', SOLVE_ORDER = 2
SELECT {[T1], [Qtr2], [semi-annual]} ON the RANKS.
{[Margin], [Total cost], [percentage]} ON COLUMNS
[EXAMPLE]. [Base]

See you soon

John
http://John-Goodwin.blogspot.com/

Tags: Business Intelligence

Similar Questions

  • MDX driver for 11g

    Hello!
    Is it possible to try the new driver for mdx for oracle 11g?

    I know it will be released shortly, but I would check how it works in our environment. I just want to know if it will be worth the effort to convince my management to this solution.
    And the decision-making process in society take a while...

    A few days ago I querried Simba Technologies for 'demo' version, but the din't get no response.

    RAF

    Published by: Rafalm1 on July 3, 2009 11:17

    Rafal thank you to send us your evaluation registration form this morning for our next product "MDX Provider for Oracle OLAP".

    I just sent you the link where you can download private a copy of the pre-release version of the software.

    We look forward to working with you and answer any questions about our great BI for Excel connector orient them to Oracle 11 g OLAP Option.

    Sincerely,
    Will of Russ, product manager, Simba Techologies
    http://www.Simba.com/MDX-provider-for-Oracle-OLAP.htm

  • "Microsoft.MDX.DemoScheduler has stopped working".

    Starting my new laptop (ex IE display Toshiba) a message box "Microsoft.MDX.DemoScheduler has stopped working" "Windows is checking for a solution to the problem."

    Then she disappears after 20-30 seconds.

    Any ideas?

    Stu

    Hello

    I received this hit when I searched in Bing:

    http://msdn.Microsoft.com/en-us/library/aa216775 (SQL.80) .aspx

    I would recommend reposting in The Forum Technet SQL Server

  • I have a wireless negear connected my labtop unable hostname querry

    I have a wireless negear connected my labtop cannot querry hostname. I have a connection, but I can't the internet upward

    Hi, Melissa,

    Repair and Winsock Reset catalog

    1. Click the Start button.
    2. Type Cmd in the search text box.
    3. Press Ctrl-Shift-Enter keyboard shortcut to run command as administrator prompt. Allow elevation request.
    4. Type netsh winsock reset in the command line shell, and then press the Enter key.
    5. Restart the computer.

    Try to use the Mr. Fixit to reset the IP stack

    How to reset the Protocol Internet (TCP/IP)

    http://support.Microsoft.com/kb/299357

    Press the Windows flag + R to open the run

    Type www.yahoo.com

    Press Ok

    This should open a Web page

  • MDX - member of DROP

    Hi all

    is it possible to drop members via MDX?

    I want to file all the members of the following query:

    SELECT

    {}

    ON COLUMNS,

    FILTER ({CONTRACTS. LEVELS (0). MEMBERS}, LEFT (CONTRACTS. CURRENTMEMBER. MEMBER_UNIQUE_NAME, 1) '[' <>)

    ON THE LINES

    OF THE APPLICATION. CUBE;

    Example of syntax for Member droping

    DROP MEMBER [booksnall]. [measures]. [percentage_increase]

    Short answer - no MDX is a query-only language.

    In fact, Essbase does not Remove easy members. If it is a one-time process and there are a large number of members that I would use the output of the query to generate a list of members, put in a flat file and then create a rule which moves all members to be children of a common "dummy", for example "DeleteMe" parent

    Then manually go and delete "DeleteMe" of the sketch, taking the children with her.

    Alternatively, you can generate a file with all members you do want to keep and rebuild the dimension with the option 'remove' not determined in a State of charge.

  • MDX tale 2 - one is much faster

    A wonderful expert Essbase (albums firm whose name starts with I?) recommended that I use this formula MDX member Bill & forecasts in the Scenario dimension:

    Case When([Actuals],[expense]) missing <>then

    [Real]

    On the other

    [ForecastScenario]

    END

    It took over 30 minutes to run, so I killed my report script.

    I have changed its MDX, which took 2 minutes:

    IIF)

    [Actuals, [expense]) missing <>]

    [Real]

    [ForecastScenario]

    )

    However, I do not know why.

    Does anyone have an idea?

    Merry Christmas and happy holidays!

    ASO queries using MDX is broken down into one or more stored queries (for example if your MDX adds two different results, it can be run as two stored queries). Apparently, Essbase called these "core applications.

    When I see variable performance for functionally identical queries the number of "core applications' produced by each of these approaches is one of the things I check.

    To do this, turn on the tracking query:

    change the database application. DB enable query_tracking;

    Run your first query (only). Then run...

    query the database application. DB get cube_size_info;

    .. .and look at statistics 'follow-up of kernel queries' in the output. Run your second query then re-issue the query database statement. Look how much 'followed the kernel queries' has increased.

    This way you can tell if one of the approaches are being broken down in addition to the nucleus than the other queries. Still doesn't explain the difference, but sometimes.

    Disable query followed later with:

    change the database application. DB disable query_tracking;

  • This simple MDX does not check

    This simple MDX of ASOsamp is not checked.

    IIF (NonEmptySubset)

    Crossjoin)

    [Real] [expenses]

    )

    [Real]

    [ForecastScenario]

    )

    This formula is a member of the worksheet titled scenario "forecast & real.

    Any suggestions on why it's a failure?

    Thank you and Merry Christmas / Happy Holidays.

    In additions to the problem with Parens, a cross join assumes two member sets that are each {} locked into what you really see is a tuple. change the nonemptyset of non-empty set and lose the cross join.

    Frankly, I find easier to read box instructions

    What is

    Case When ([Actuals], [expense]) <> lack then

    [Atuals]

    On the other

    [Load]

    END

  • Stupid MDX script takes more than 10 hours to run in ASO

    I inherited a stupid MDX takes more than 10 hours to run in ASO. This formula is member of the map called forecast scenario & real scenario.

    This is the equivalent of ASOsamp of it:

    I think I can shorten it to:

    (1) are the following equivalent?

    IIF (([ActualScenario],[Expense]) + 0 <>0)

    can be replaced by

    IIF (NonEmptySubset ([ActualScenario], [Expense])

    ?

    2)

    The reason I can remove almost all the lines for the PERIOD - his first line, it is already check if [period] is zero. Then, it updates level 0.

    So why would we want to write the code to update (period) levels 1, 2 and 3?  ASO is supposed to automatically consolidate all other levels 1 to 3. So why is this MDX aggregating levels 1 to 3?

    (3) in fact, I don't know why we need this Case statement:

    CASE WHEN ISLEVEL ([period]. CurrentMember, 0)

    I thought THAT MDX in Member roadmap scenario only works on members leaves (zero level).

    PS.

    The time dimension is simply

    Year

    -T1

    -Jan

    -Feb

    -Mar

    -Qtr2

    etc.

    Thank you and Merry Christmas / happy holidays!

    PS. I changed my name to "SEEP limits."

    Rolling up the quarters is the real problem. Since you have a verification statement to see if you are at level 0 do the math, you're cutting everything above level 0. Yes, it's fast - but it's because you're excluding senior level members.

    I don't know how this cube is great, but you can possibly use this formula with a procedure calc to write the data to another Member. In this way the aggregation would work without any formula.

  • Changing a dimension of stored to ASO dynamics will change my Calc MDX results?

    Merry Christmas / Happy Holidays!

    Changing a dimension of stored to ASO dynamics will change my Calc MDX results?

    Has anyone turn their dimensions of dynamic Stored?  What are the problems that you have experienced?

    Thank you for the early Christmas present (with answers).

    As suggested by the other responses, it depends in part why you change.

    As Philippe said, the potential problem is calculation order. Stored dimensions are always grouped before the member formulas / dynamic dimensions.

    If you do everything is change a dimension currently stored is dynamic (i.e. you don't change consolidation properties, or add formulas) and then you end up with a dynamic dimension with all members having a resolution of zero order. "The order of resolution" is a property that controls the order of calculation and extends from 0 to 127.

    This can change calculation results if you have existing dynamic members who also solve orders from scratch, because the solve order "tie" is broken by order reverse contour of the dimensions.

    So if you change a dimension currently stored in dynamic and it appears in the sketch after (lowest in the Outline Editor view) all other dynamic dimensions (or all your other dynamic dimension members have an order of resolution greater than zero), you're safe; There is certainly no change in behavior. If you change a dynamic currently stored dimension and there are other sides dynamic after him in the sketch that contain zero members to resolve, you should test.

    Further details on the order of calculation ASO in the database administrator's Guide: ASO calculation order

    * I leave aside the extremely rare case where you set orders non-zero address stored dimension, that (unfortunately) Essbase allows to perform, despite the fact it has no effect whatsoever - orders to solve without meaning survive the dynamic conversion and become meaningful.

  • Change the size of compression to ASO will do my Calc MDX results change?

    Merry Christmas / Happy Holidays!

    Change the size of compression to ASO will do my Calc MDX results change?

    Our EAS reported this: our dimension of reduction measures to the switching times will be half of our data file size.  Has anyone turn their dimensions of compression?  What are the problems that you have experienced?

    Thank you for the early Christmas present (with answers).

    This is not a duplicate, but it's largely the same question that a dynamic dimension to ASO stored passing Will do my Calc MDX results change?

    This is because the size of compression must be dynamic, so if you select a dimension that is currently stored in the size of the compression, it will be converted to dynamic.

    If you change the size of the compression of an already dynamic dimension, it has certainly no effect.

  • How formula MDX on level zero member data to Smartview?

    Hi Experts,

    I'm a member of level zero, which stores the data AND formula MDX to ASO.  I wonder what happens when I pick up this member using Smartview?  ASO runs this formula, stores the result in the form of data in this member (zero level) - then report stored data to Excel? In other words - how formula MDX on members level report data zero to Smartview?

    Merry Christmas / Happy Hanakkuk (and all other religious holiday greeting comes to be PC).

    Ho Ho Ho!

    Level 0 members not also store data, if it has an MDX formula. The value is calculated according to the formula only at the time of the recovery.

  • Calc scripts MDX on ASO is 20 x slower than calc on OSB?

    Is it true that calc scripts MDX on ASO's 20 x slower than calc on OSB?

    Our consultants Essbase dear wrote in their e-mail and training documents. I've never heard of this.

    Built a cube BSO staging area, loads all data source BSO. Run BSO Calc staging cube before exporting the level zero to ASO.  Is this crazy?

    Thank you.

    STOP THINKING LOT

    I agree with most of the responses seen above and actually works to understand that the ASO procedural process Calc uses during execution of their work.  This will help us all understand what kind of scripts will be quick and that are frighteningly slow.

    But, my first suggestion seeing most of the manuscripts I am presented with is: why are you using a calc script at all?  Calc scripts are often used when there is no higher level subtotals.  Well, they are always available to ASO.  The way I see it is calc scripts are really necessary when new data of level 0 must be generated and rolled up.  Or in the simple case of copies of data.

    Currency conversion is where they are most often used.  I can't convert each of the 5mm values that contribute to a higher level of $100 mm in order to convert $100 to 91,882,223 euros.  And, often copies of data are not really necessary, especially "real."  Conceivably contours where the plans and forecasts are dynamically seeded with latest figures real or actual same prerequisite.

    So look hard at your old practices first and Rob it of your scripts, anything that can be written as a successful formula of Member.  If nothing else the code remaining will most likely run faster.

    Note: Calc script processing involves the internal tree in which each dat file is organized.  I encourage anyone with an overview of this structure to communicate with me and maybe we can share observations.

  • Question MDX

    Hi all

    When I run an MDX query on one of my ASO system application get crashed. I don't know what goes wrong, but when I run the script via the service console Regional I see the following in the log file error message.

    [26 Nov 03:11:06 game 2013] Local/XXX/XXX/1306822976/Error (1200601)

    Not enough memory to run of formula. Set the MAXFORMULACACHESIZE configuration parameter [2106] KB and try again

    [26 Nov 03:11:06 game 2013] Local/xxx/xxx/1306822976/Error (1200467)

    Formula runtime error [definition of REGION]: status [1200601] code in [function]

    After that, there is no update in the log file, so I don't know if it works or not. So I killed the process ID of request assuming it was in the suspended state.

    Could someone help me please on that to overcome this problem. JohnGoodwin

    Were you able to watch the following support document? As stated in the error, you must increase the value for MAXFORMULACACHESIZE

    Error (1200601) not enough memory for execution of formula. Set the MAXFORMULACACHESIZE configuration parameter"during the execution of calculation (Doc ID 1521864.1)

    SP

    Please mark helpful or correct answers for others to answer easily.

  • MDX report script...

    Hello

    I am writing some MDX queries via trying to convert remaining report Script.

    Orders of there is an amount in report Script that I've found equivalent in MDX, in particular command TEXT

    < INSTALL {TabDelimit} {decimal number 10} {IndentGen-4} < ACCON < SYM < CITY < END

    < PAGE ("CHANNEL", "REGION", "ENTITY", "PRODUCT")
    < COLUMN ("METRICS")
    < ROW ("TIME", "WEEK")

    Members page
    {SUPPAGEHEADING}
    Members of the column

    Line members


    {JUMP 4}
    {TEXT 10 'HOME'}
    {TEXT 10 'REGION'}
    < UDA ('TIME', LOCAL_REGION)
    < UDA ('WEEK', LOCAL_REGION)
    !

    Thank you

    Hello

    All formatting problems were finally solved in the VBA code.

    So, problem solved

    Thank you

    Best regards

  • Question MDX to ASO, to token syntax error on - Urgent

    Hi All-

    I am facing a problem in the MDX script during the cleaning of a data in ASO region.

    change the database 'REP_ASO'.' REP_ASO1' clear data region ' Crossjoin (Descendants ([Engineering Group], [entity]. Levels (0)), Crossjoin ({[man-month]}, Crossjoin ({[CSA]}, Crossjoin ({[USD]}, Crossjoin (MemberRange ([period].)))) [Apr], [period]. [Tue]), MemberRange ([year]. [& FcstYear0], [year]. ((([& FcstYear1])))' Physics;

    It gives me the error, the line syntax: token 1 ON.

    Need urgent suggestion on it.

    Thank you

    you are missing one of the parenthesis at the end of the CrossJoin test this:

    change the database 'REP_ASO'.' REP_ASO1' clear data region ' Crossjoin (Descendants ([Engineering Group], [entity]. Levels (0)), Crossjoin ({[man-month]}, Crossjoin ({[CSA]}, Crossjoin ({[USD]}, Crossjoin (MemberRange ([period].)))) [Apr], [period]. [Tue]), MemberRange ([year]. [& FcstYear0], [year]. [& FcstYear1])))' Physics;

Maybe you are looking for