MDX calculated measure slow when adding operations
I have created a calculated measure through BIDS in a SSAS cube and it's like the following:
IIF([Measures].[RatePct] >= 0.90, [Measures].[measureA], [Measures].[measureB])
The point is that if I convert the above to this:
IIF([Measures].[RatePct] >= 0.90, [Measures].[measureA], 0)
or that:
IIF([Measures].[RatePct] >= 0.90, [Measures].[measureA] + 100, [Measures].[measureB])
the measure becomes extremely slow when using it in the cube.
Any ideas why this is happening and how can it be addressed?
Many thanks
mdx mdx-query
add a comment |
I have created a calculated measure through BIDS in a SSAS cube and it's like the following:
IIF([Measures].[RatePct] >= 0.90, [Measures].[measureA], [Measures].[measureB])
The point is that if I convert the above to this:
IIF([Measures].[RatePct] >= 0.90, [Measures].[measureA], 0)
or that:
IIF([Measures].[RatePct] >= 0.90, [Measures].[measureA] + 100, [Measures].[measureB])
the measure becomes extremely slow when using it in the cube.
Any ideas why this is happening and how can it be addressed?
Many thanks
mdx mdx-query
add a comment |
I have created a calculated measure through BIDS in a SSAS cube and it's like the following:
IIF([Measures].[RatePct] >= 0.90, [Measures].[measureA], [Measures].[measureB])
The point is that if I convert the above to this:
IIF([Measures].[RatePct] >= 0.90, [Measures].[measureA], 0)
or that:
IIF([Measures].[RatePct] >= 0.90, [Measures].[measureA] + 100, [Measures].[measureB])
the measure becomes extremely slow when using it in the cube.
Any ideas why this is happening and how can it be addressed?
Many thanks
mdx mdx-query
I have created a calculated measure through BIDS in a SSAS cube and it's like the following:
IIF([Measures].[RatePct] >= 0.90, [Measures].[measureA], [Measures].[measureB])
The point is that if I convert the above to this:
IIF([Measures].[RatePct] >= 0.90, [Measures].[measureA], 0)
or that:
IIF([Measures].[RatePct] >= 0.90, [Measures].[measureA] + 100, [Measures].[measureB])
the measure becomes extremely slow when using it in the cube.
Any ideas why this is happening and how can it be addressed?
Many thanks
mdx mdx-query
mdx mdx-query
asked Nov 12 '18 at 23:37
Yiannis AYiannis A
32
32
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
That is because in both cases you are returning values that were earlier a possible null. Now the number of empty combinations have decreaded. Consider a case where [Measures].[measureA] was null but since you now have [Measures].[measureA] + 100 this will return 100 as a value. Now you UI will not be able to remove it as a null combination
Thanks! it's pretty much that. I managed though to make it quick with the below workaround: [Measures].[measureA] + 100*([Measures].[measureA]/[Measures].[measureA]) Now, it became very fast...
– Yiannis A
Nov 26 '18 at 14:02
You are welcome. You might want to consider marking my suggestion as answer
– MoazRub
Nov 26 '18 at 15:01
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271679%2fmdx-calculated-measure-slow-when-adding-operations%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
That is because in both cases you are returning values that were earlier a possible null. Now the number of empty combinations have decreaded. Consider a case where [Measures].[measureA] was null but since you now have [Measures].[measureA] + 100 this will return 100 as a value. Now you UI will not be able to remove it as a null combination
Thanks! it's pretty much that. I managed though to make it quick with the below workaround: [Measures].[measureA] + 100*([Measures].[measureA]/[Measures].[measureA]) Now, it became very fast...
– Yiannis A
Nov 26 '18 at 14:02
You are welcome. You might want to consider marking my suggestion as answer
– MoazRub
Nov 26 '18 at 15:01
add a comment |
That is because in both cases you are returning values that were earlier a possible null. Now the number of empty combinations have decreaded. Consider a case where [Measures].[measureA] was null but since you now have [Measures].[measureA] + 100 this will return 100 as a value. Now you UI will not be able to remove it as a null combination
Thanks! it's pretty much that. I managed though to make it quick with the below workaround: [Measures].[measureA] + 100*([Measures].[measureA]/[Measures].[measureA]) Now, it became very fast...
– Yiannis A
Nov 26 '18 at 14:02
You are welcome. You might want to consider marking my suggestion as answer
– MoazRub
Nov 26 '18 at 15:01
add a comment |
That is because in both cases you are returning values that were earlier a possible null. Now the number of empty combinations have decreaded. Consider a case where [Measures].[measureA] was null but since you now have [Measures].[measureA] + 100 this will return 100 as a value. Now you UI will not be able to remove it as a null combination
That is because in both cases you are returning values that were earlier a possible null. Now the number of empty combinations have decreaded. Consider a case where [Measures].[measureA] was null but since you now have [Measures].[measureA] + 100 this will return 100 as a value. Now you UI will not be able to remove it as a null combination
answered Nov 25 '18 at 0:10
MoazRubMoazRub
31927
31927
Thanks! it's pretty much that. I managed though to make it quick with the below workaround: [Measures].[measureA] + 100*([Measures].[measureA]/[Measures].[measureA]) Now, it became very fast...
– Yiannis A
Nov 26 '18 at 14:02
You are welcome. You might want to consider marking my suggestion as answer
– MoazRub
Nov 26 '18 at 15:01
add a comment |
Thanks! it's pretty much that. I managed though to make it quick with the below workaround: [Measures].[measureA] + 100*([Measures].[measureA]/[Measures].[measureA]) Now, it became very fast...
– Yiannis A
Nov 26 '18 at 14:02
You are welcome. You might want to consider marking my suggestion as answer
– MoazRub
Nov 26 '18 at 15:01
Thanks! it's pretty much that. I managed though to make it quick with the below workaround: [Measures].[measureA] + 100*([Measures].[measureA]/[Measures].[measureA]) Now, it became very fast...
– Yiannis A
Nov 26 '18 at 14:02
Thanks! it's pretty much that. I managed though to make it quick with the below workaround: [Measures].[measureA] + 100*([Measures].[measureA]/[Measures].[measureA]) Now, it became very fast...
– Yiannis A
Nov 26 '18 at 14:02
You are welcome. You might want to consider marking my suggestion as answer
– MoazRub
Nov 26 '18 at 15:01
You are welcome. You might want to consider marking my suggestion as answer
– MoazRub
Nov 26 '18 at 15:01
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53271679%2fmdx-calculated-measure-slow-when-adding-operations%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown