Hot answers tagged

7

As you correctly noted this is what happens when you try to display measures across a dimension to which they don't have a relation. You basically have 2 options Use IgnoreUnrelatedDimensions Use an MDX solution I would suggest you try the IgnoreUnRelatedDimensions first, as the measures would be aggregated better, and NonEmptyCrossJoins would be able ...


3

Please try this format string: 0,,.0 \M $ This trick is a bit buried in the documentation.


3

In SSMS if you open each role and find the Measures Dimension Data security section then go to the Advanced tab (if you have trouble finding it see this blog for screenshots from the same screens in SSDT-BI) do you see any role mentioning that problem measure? If that measure doesn't exist in the cube then remove it from the security role definition. If ...


3

That's right. The cube browser control within SSDT is completely different to the one that used to exist in BIDS2008 or lower. This had me going at first too. The best way i found to get around this was to launch into excel, which can be done from the cube browser tab. I believe it even creates a temporary connection file for you too so you don't have to ...


2

Every object has a Name and ID property that must be unique within the scope of the parent collection. For example, two dimensions can have same name as long as each one resides in a different database. A database is a scope. A cube is an object. Two cubes can have same name or ID as long as they belong to different databases. Although you can specify it ...


2

The solution was removing the empty files E:\MSAS11.DWH_AS\OLAP\Data\Cube Fraude.0.db\MY_DATABASE OLAP.56.cub.xml which allowed the aggregation to continue


2

Add this calculated measure to the cube: Create Member CurrentCube.[Measures].[Max Current CP With Units] as IIf(Not IsEmpty([Measures].[Units]),[Measures].[Max Current CP],Null);


1

from the SQL management studio, connect to Analysis services and go to Roles, under the roles, the user that has been removed from active directory will appear in question marks "????????????????" , remove him and reprocess the cube


1

You just need to add an MDX where clause. Look at the Basic MDX syntax. In that where you need to specify the SET to slice on. Have a look at Using Sets in MDX Queries SELECT NON EMPTY { [Measures].[Order Ref Product Count] } ON COLUMNS, NON EMPTY { ([Product].[Product ID].[Product ID].ALLMEMBERS ) } ON ROWS FROM [Sales] WHERE {[Product].[Product ID].[3]...


1

You should calculate this during your ETL process or create a calculated column on your fact table. Then, aggregations will be easier and queries will be somewhat faster than calculating the values at runtime.


1

MSDN states: The value of the AttributeHierarchyEnabled property determines whether an attribute hierarchy is created. If this property is set to False, the attribute hierarchy is not created and the attribute cannot be used as a level in a user hierarchy; the attribute hierarchy exists as a member property only. However, a disabled attribute hierarchy ...


1

Oh my dear.. First of all. In your case I would like to suggest you to choose the "Process Default" option. If you are using Process Full always you are dropping all data and objects and recreating all of your stuff. You don't need them. Very often the proposal option is to use ProcessData followed by ProcessIndex. I didn't proces the cube from within the ...


1

First, I suggest you read about star schema first. Not understanding the concepts could lead to wrong results. You may use the transaction as your fact table as in the diagram below. Don't use DISTINCT, instead you want to use: SELECT ... FROM fact GROUP BY dimension data (time, transaction and bank) WHERE condition to restrict dimension data and join ...



Only top voted, non community-wiki answers of a minimum length are eligible