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 to ...
5
I think you are confusing things.
First of all, processing the cube and processing the dimensions is sort of separate. I think you mean "processing the entire database".
If you process only dimensions, and not the cube, the measures will never be updated.
You could Process Update the dimensions which wouldn't unprocess the cube but would drop the indexes ...
3
Please try this format string:
0,,.0 \M $
This trick is a bit buried in the documentation.
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 ...
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 ...
2
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 ...
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);
2
This is an overly broad question but SSAS has security features that allow you to shield data for certain users.
You should look into Roles and Permissions.
Since you are talking about shielding costs you probably just want to limit access to certain measures so you're probably looking for Grant custom access to cell data which limit access to the values:
...
2
If you want to make sure the code you are running is exactly the code run when you process manually you should click the script button in SSMS and use that XMLA script. If you execute a series of steps you should script each step.
This will generate the scripts as XML so you can execute in SSMS and that will 100% do the same as clicking the OK button on the ...
2
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
Mondrian is indeed a good example, in that it's a ROLAP engine (in which MDX statements are translated to SQL which are then fired to the underlying database (other than it caches results, so ends up being a Hybrid approach instead of pure ROLAP).
However, the "translation" between MDX and SQL isn't a straightforward one. A lot of MDX statements require ...
1
Did you read the rest of the docs?
Output when running DBCC against an earlier version of Analysis
Services
DBCC is only supported on databases running on a SQL Server 2017
instance. Running the command on older systems will return this error.
Executing the query ...
The DBCC element at line 7, column 87 (namespace http://schemas.microsoft.com/...
1
The Customer dimension is joined to the measure group at a non-key granularity. If the Customer Name attribute isn't related to the attribute you join on then data repeats in reports. You need to do one of two things:
Recommended. Change the fact table to have the surrogate key of the dimension. Then change the Dimension Usage tab to join to the key of the ...
1
First you need two cube-dimensions because you cannot use one dimension on more than one axe of a MDX-select. You can use role-playing dimensions, that means there is only one "Week" dimension in the database but it is used twice with different names for the cube.
Second each Week dimension has to be connected to a measure group. If you use only one measure ...
1
You have a product dimension using all 3 tables. The dimension key is DimSellableItemVersion.SellableItemId and you can use SellableItemAvailability.Id two times as an attribute, once for the product and once for the parent-product. But SSAS does not know which is which or when you want to use it only once, which on you mean. Do you want to go left or right ...
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
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 ...
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 ...
Only top voted, non community-wiki answers of a minimum length are eligible
