Showing posts with label mdx. Show all posts
Showing posts with label mdx. Show all posts

Friday, March 30, 2012

OLAP cube - formula length

Hi

dear all,

does anybody know the maximum length for an mdx formula for a calculated member in SSAS?

Kind regards

Frederikm

No hard limit in SSAS 2005.|||

Hi

i find this kind of hard to believe...

I have a formula with over 4000 characters... processing this cube is impossible

the formula is a formula in the form of iif(errorcheck, 0, iif(errorcheck,0... etc

if i use the basic formula without the iif's the cube processes without any problems....

Kind regards

|||There is a syntax error in your formula somewhere, and the error message should give you an idea about location of this error. The syntax error is the real cause of why your cube doesn't deploy, not the length of the formula.|||

Hi

about the max length: is this tied to any service pack version? we are using sp1
also the thing is that there is no error in the formula,
for when we use it in a normal mdx query it works without any problem...
only when in the cube things go wrong

|||The fact that it works inside MDX query means that there is no problem with the length. What is the exact error message you are getting when you are trying to deploy cube with such calculated member ?

Monday, March 26, 2012

offline OLAP Cube +MDX

I will be really very much greatful to one who can help me out as I have been struggling to solve this from 2 months.

I have a .mdb database and I want to craete a pivot from it.The size of the database is around 400 MB so it was suggested to create a cube from this database and then create pivot.The database is populated with TOTAL values for all its class variables .

When I create cube from Excel wizard it again summarises and craetes ALL level and the pivot is completely wrong.Infact I get values in the multiples of 2**classvariables.Is there a way where can I create cube by VBA and eliminate ALL LEVEL for every dimension. I have tried so many codes but nothing is working.Any sample code will be a great help.

Here I am getting Multiple Selections for page field as well .Is there any way to disable them?

The second option could be to populate the Listviews with the dimension values and then create a report in Excel using MDX but its not working as well.

I am relly looking looking forward to you great guys.

Regards

Hi,

create the cube with the Excel-Wizar. Save the to C:\

Then there is a SclicerDDL.txt with the CREATE GLOBAL Cube-Statement.

Remove the All Level

Example:

DIMENSION [CUBENAME].[DIM-NAME]
(
LEVEL [(All)], <-Delete this line
LEVEL [L1],
LEVEL [L2],
LEVEL [L3],
LEVEL [L4]
)

>

DIMENSION [CUBENAME].[DIM-NAME]
(
LEVEL [L1],
LEVEL [L2],
LEVEL [L3],
LEVEL [L4]
),

Run this edited SlicerDDL.txt in the Analysis Server MDX-Samples and the local cube will not contain the All-Level.

hth

Bernhard Saemmer

|||I only have Excel in my machine.Is it possible to do it by VBA?

offline OLAP Cube +MDX

I will be really very much greatful to one who can help me out as I have been struggling to solve this from 2 months.

I have a .mdb database and I want to craete a pivot from it.The size of the database is around 400 MB so it was suggested to create a cube from this database and then create pivot.The database is populated with TOTAL values for all its class variables .

When I create cube from Excel wizard it again summarises and craetes ALL level and the pivot is completely wrong.Infact I get values in the multiples of 2**classvariables.Is there a way where can I create cube by VBA and eliminate ALL LEVEL for every dimension. I have tried so many codes but nothing is working.Any sample code will be a great help.

Here I am getting Multiple Selections for page field as well .Is there any way to disable them?

The second option could be to populate the Listviews with the dimension values and then create a report in Excel using MDX but its not working as well.

I am relly looking looking forward to you great guys.

Regards

Hi,

create the cube with the Excel-Wizar. Save the to C:\

Then there is a SclicerDDL.txt with the CREATE GLOBAL Cube-Statement.

Remove the All Level

Example:

DIMENSION [CUBENAME].[DIM-NAME]
(
LEVEL [(All)], <-Delete this line
LEVEL [L1],
LEVEL [L2],
LEVEL [L3],
LEVEL [L4]
)

>

DIMENSION [CUBENAME].[DIM-NAME]
(
LEVEL [L1],
LEVEL [L2],
LEVEL [L3],
LEVEL [L4]
),

Run this edited SlicerDDL.txt in the Analysis Server MDX-Samples and the local cube will not contain the All-Level.

hth

Bernhard Saemmer

|||I only have Excel in my machine.Is it possible to do it by VBA?