Different complexity of data extraction from cube(SSAS 2015) via excel 2013
When user connect to SSAS cubes 2015(cube size is approx 15-16 GB) from excel 2013. they browse the cube data by selecting the different combination of dimensions attributes and facts measures.
This combination in excel to fetch the cube data can be simple or complex.
I have a requirement from client where I have to come up with the different types of these combination to fetch data which can be described as Simple, Moderate and Complex.
[For example(I have to come up with something like this): 1. fetching data for less than 5 measures within the same measure group against less than 10 dimension is Simple Extraction.
2. Fetching data for more than 5 and less than 10 measures against more than 10 dimesions within the same measure group is moderateExtraction.
3. fetching ata for more than 10 measure across multiple measure groups against more than 15 multiple dimensions attributes considered as Complex Extraction]
Do anyone has any experience /knowledge/idea on working on such type of request. Any comment / idea / suggestion will be a great help.
excel ssas mdx cube data-extraction
add a comment |
When user connect to SSAS cubes 2015(cube size is approx 15-16 GB) from excel 2013. they browse the cube data by selecting the different combination of dimensions attributes and facts measures.
This combination in excel to fetch the cube data can be simple or complex.
I have a requirement from client where I have to come up with the different types of these combination to fetch data which can be described as Simple, Moderate and Complex.
[For example(I have to come up with something like this): 1. fetching data for less than 5 measures within the same measure group against less than 10 dimension is Simple Extraction.
2. Fetching data for more than 5 and less than 10 measures against more than 10 dimesions within the same measure group is moderateExtraction.
3. fetching ata for more than 10 measure across multiple measure groups against more than 15 multiple dimensions attributes considered as Complex Extraction]
Do anyone has any experience /knowledge/idea on working on such type of request. Any comment / idea / suggestion will be a great help.
excel ssas mdx cube data-extraction
add a comment |
When user connect to SSAS cubes 2015(cube size is approx 15-16 GB) from excel 2013. they browse the cube data by selecting the different combination of dimensions attributes and facts measures.
This combination in excel to fetch the cube data can be simple or complex.
I have a requirement from client where I have to come up with the different types of these combination to fetch data which can be described as Simple, Moderate and Complex.
[For example(I have to come up with something like this): 1. fetching data for less than 5 measures within the same measure group against less than 10 dimension is Simple Extraction.
2. Fetching data for more than 5 and less than 10 measures against more than 10 dimesions within the same measure group is moderateExtraction.
3. fetching ata for more than 10 measure across multiple measure groups against more than 15 multiple dimensions attributes considered as Complex Extraction]
Do anyone has any experience /knowledge/idea on working on such type of request. Any comment / idea / suggestion will be a great help.
excel ssas mdx cube data-extraction
When user connect to SSAS cubes 2015(cube size is approx 15-16 GB) from excel 2013. they browse the cube data by selecting the different combination of dimensions attributes and facts measures.
This combination in excel to fetch the cube data can be simple or complex.
I have a requirement from client where I have to come up with the different types of these combination to fetch data which can be described as Simple, Moderate and Complex.
[For example(I have to come up with something like this): 1. fetching data for less than 5 measures within the same measure group against less than 10 dimension is Simple Extraction.
2. Fetching data for more than 5 and less than 10 measures against more than 10 dimesions within the same measure group is moderateExtraction.
3. fetching ata for more than 10 measure across multiple measure groups against more than 15 multiple dimensions attributes considered as Complex Extraction]
Do anyone has any experience /knowledge/idea on working on such type of request. Any comment / idea / suggestion will be a great help.
excel ssas mdx cube data-extraction
excel ssas mdx cube data-extraction
asked Nov 22 '18 at 3:04
ScriptSoftScriptSoft
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I faced a similar issue quite a long time back. The situation was we made an in house cube browser (something along the lines of what opens up when we select the browse option in SSMS). The MDX generator for this was also written in-house, so we used to add in functionality when we faced difficult requirements. But with off the shelf tools, you cannot push the MDX they emit. And as the users select more and more combinations the query will not be optimal at all. Therefore I suggest that you let them use excel for the basic or moderate level at most. For the complex level you should provide them custom MDX, where based on your business knowledge, you can filter out irrelevant combinations. Plus you can paginate your query.
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%2f53423280%2fdifferent-complexity-of-data-extraction-from-cubessas-2015-via-excel-2013%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
I faced a similar issue quite a long time back. The situation was we made an in house cube browser (something along the lines of what opens up when we select the browse option in SSMS). The MDX generator for this was also written in-house, so we used to add in functionality when we faced difficult requirements. But with off the shelf tools, you cannot push the MDX they emit. And as the users select more and more combinations the query will not be optimal at all. Therefore I suggest that you let them use excel for the basic or moderate level at most. For the complex level you should provide them custom MDX, where based on your business knowledge, you can filter out irrelevant combinations. Plus you can paginate your query.
add a comment |
I faced a similar issue quite a long time back. The situation was we made an in house cube browser (something along the lines of what opens up when we select the browse option in SSMS). The MDX generator for this was also written in-house, so we used to add in functionality when we faced difficult requirements. But with off the shelf tools, you cannot push the MDX they emit. And as the users select more and more combinations the query will not be optimal at all. Therefore I suggest that you let them use excel for the basic or moderate level at most. For the complex level you should provide them custom MDX, where based on your business knowledge, you can filter out irrelevant combinations. Plus you can paginate your query.
add a comment |
I faced a similar issue quite a long time back. The situation was we made an in house cube browser (something along the lines of what opens up when we select the browse option in SSMS). The MDX generator for this was also written in-house, so we used to add in functionality when we faced difficult requirements. But with off the shelf tools, you cannot push the MDX they emit. And as the users select more and more combinations the query will not be optimal at all. Therefore I suggest that you let them use excel for the basic or moderate level at most. For the complex level you should provide them custom MDX, where based on your business knowledge, you can filter out irrelevant combinations. Plus you can paginate your query.
I faced a similar issue quite a long time back. The situation was we made an in house cube browser (something along the lines of what opens up when we select the browse option in SSMS). The MDX generator for this was also written in-house, so we used to add in functionality when we faced difficult requirements. But with off the shelf tools, you cannot push the MDX they emit. And as the users select more and more combinations the query will not be optimal at all. Therefore I suggest that you let them use excel for the basic or moderate level at most. For the complex level you should provide them custom MDX, where based on your business knowledge, you can filter out irrelevant combinations. Plus you can paginate your query.
answered Nov 22 '18 at 18:24
MoazRubMoazRub
28427
28427
add a comment |
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%2f53423280%2fdifferent-complexity-of-data-extraction-from-cubessas-2015-via-excel-2013%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