Dimension usage relationship between dimensions

Hi,
please I have a case where an attribute of a dimension is part of the measure in a report, How can I establish a dimension usage relationship between this table and other dimension that is related as below( whereby the supposed fact table primary key is
appearing as foreign key in the dimension table). Thanks
ACCOUNT TABLE
accid -PK
EXTRAS TABLE
accid -FK

Hi 14QR1A,
According to your description, you want to build the relationship between dimension tables. Right?
In Analysis Services, it can have relationship between dimension like some snowflake schema. In BIDS, you can direct build the relationship between dimension tables in Data Source View. For example, the ProductCategory has relationship with
ProductSubCategory in AdventureWorks sample.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou
TechNet Community Support

Similar Messages

Relationship between dimensions

hi everyone,
we are facing slight design issue in our datawarehouse. Is it a fair idea to have relationship between two dimensions? actually one dimension is related to other dimensions in SCD implementation. e.g. customer changes his products over time. so product dim key needs to be present in customer dimension table. is this type of design ok ?
TIA

Hi Yogesh,
I guess the question is really what you intend on doing with this relationship...? I guess there are a couple of ideas on this:
1) The dimension is actually customer products, not so much customer or product. Note you may have a separate customer dimension to store all the addresses. In that case your key to products would duplicate the customer key and you would have to make sure that they are derived from the same records source in order to ensure that the fact record links to the same customer as in customerproducts dim.
2) You really only want to make sure that the product code you store with the customer is a valid one. In that case you just have a reference table (which happens to be a dimension) in the ETL process. You can implement this a ref integrity between the 2 tables...
3) You want to somehow use this in your query tool. Than I think it may be worthwhile to consider option1.
If you are thinking relationships, and you do not necessarily want users to query your model, you may want to consider a slightly normalized data store model.
So I guess you can go many ways, but in the end this is driven by what you need to do with this information.
Hope this makes some sense, feel free to push this discussion along :-)
Jean-Pierre

One to One relationship between Dimensions and Fact Tables

Hi,
Not a real Discoverer question, but seeing as there is such a huge pool of talent here, I thought I'd ask anyway...
Is the concept of having a one to one join between a Dimension and a Fact Table an Acceptable Thing (tm). I'm not talking about a degenerate dimension, as the Dimension would hold additional attributes.
It's something I'm trying to get my head around and would appreciate any viewpoints.
Thanks,
Andy

Hi Andy,
There is of course no distinction in SQL between 1-1 and 1-n joins, but in your database design you would avoid denormalizing data into a dimension table if it was only ever used once.
From a Discoverer perspective setting the join to 1-1 controls how aggregate queries are constructed. Normally, if you have a master-detail 1-n relationship and you aggregate items in both tables then you will get an incorrect result for the master table because the number of rows are multipled by the n detail records. Similarily if you have 2 detail tables in the query and you aggregate items in a detail table you will get incorrect results. Discoverer recognises these situations and raises an error.
Setting the join as 1-1 tells Discoverer that it will get the correct results in these situations and therefore no error is raised. So it is perfectly acceptable to set the joins as 1-1 as long as you know the implications.
Hope that helps,
Rod West

Relationship between Dimension without linking Fact table

Hi,
My question is like I have five dimensions connected to a fact table through primary - foreign key(Composite Key) relationship. Will this referential integrity help if I want some information between two dimension which are not linked directly and I am not
including any measures from fact table .
Example: Suppose I have customer, Product and Manufacturer Dimensions all linked to a fact table but not linked to each other directly but can I get right result when I want to know what are the manufacturer for each product? or list of
customers using a particular product. Will the referential integrity work ? since they all are related in fact table.
regards
Sanjoy ghosh

Hi Sanjoy -
The answer to your questions depends on your dimensional design and exactly what the fact table represents. Fact tables naturally capture the intersection of the different dimensions. This is true whether you physically implement a
PK - FK relationship in the relational db.
In your case, since customer is involved, sounds like a sales transaction fact. If that's true, you can easily join from customer, through the fact, to the product dimension, to get the list of customers that purchased a particular product.
For the manufacturer for each product, a sales transaction fact will not necessarily answer this question completely. Particularly in the case of products that have no sales for a given period, and thus, don't have any fact records to join from manufacturer
across to product. If you need to solve this question, you have some other options:
- flatten the Manufacturer directly into the Product dimension as attribute of the product (probably the simplest approach and allows you to remove a key from the fact)
- embed the Manufacturer key directly in the Product dimension (if you need the Manufacturer dimension separate for use with other events / facts and more detailed dimensionality - i.e., detailed attributes about the Manufacturer that wouldn't need
to be flattened onto the product)
- build a factless fact that captures the products offered by a given manufacturer at a given point in time (perhaps representing various products catalogs and associated dates. This would allow you to capture rich details about each dimension separately
and use the factless fact to record)
Let me know if that helps.
Brent Greenwood, MS, MCITP, CBIP
// Please mark correct answers and helpful posts //
http://brentgreenwood.blogspot.com

Many to many relationships between Fact and Dimension

Hi All,
I have to solve two kind of many to many relationships between Fact and Dimension.
1. Many to Many relationship between Fact and Dimension, using a bridge table, with FKs in fact and dimension to bridge tables PK.
2. Many to Many relationship between Fact and Dimension, using a bridge table, and an intersection table, with FK in fact to bridge table, and 2 FKs in intersection table to Dimension and to bridge table.
I need help on implementing (how the mapping has to look like) them in OWB 9.2.0.2.8.
Thanks,
Aurelian Cojocaru

Aurelian,
Unfortunately, you cannot implement this in the dimensional model. You would have to use relational tables and relationships between those in order to implement your scenario.
Thanks,
Mark.

BIDS 2008 - Dimension Usage new relationship Measure Group Column list empty?

Ive been updating my underlying schema, and DSV and now Im having to update some of the Dimensions. Looks like things got a bit "sideways" somewhere along the way. Now that Im going back to reassign dimensions being used within the
Dimension Usage tab of the Cube, the measure group column list is empty when I go to create a new relationship (regular type)

Hi shiftbit,
According to your description, you get an empty Measure Group Columns list when defining relationship. Right?
Based on your screenshot, you may notice that Measure group table is empty, so definitely it can't show any column in the dropdown list. If there's columns in the measure group that are related to the dimension columns, at least it will show the fact
table for Measure group.
In this scenario, please check if the fact table for the Measure group is existing. Re-process the Measure group and try again. If the issue persists, please re-create that measure group.
Reference:
Define Relationship Dialog Box (Analysis Services - Multidimensional Data)
If you have any question, please feel free to ask.
Best Regards,
Simon Hou
TechNet Community Support

Is it possible to ignore "Rigid relationships between attributes cannot be changed" when using ProcessUpdate for Dimension?

As per the title is it possible to ignore "Rigid relationships between attributes cannot be changed" when using ProcessUpdate for Dimension?
We have a case where very rarely an item might have been miscategorised so the brand is manually changed. We want this dimension to be rigid to speed up ProcessUpdate.
We do a ProcessFull each night, so it will get corrected then, but during the hourly updates we would just like to ignore this error if possible?

Hello,
The rigid relationship should be defined when the members will not change over time. Here are some threads regarding rigid relationship for your reference, please see:
Processing OLAP Cube: http://social.technet.microsoft.com/Forums/sqlserver/en-US/17a55593-9543-404e-a579-0a011965585d/processing-olap-cube?forum=sqlanalysisservices
Flexible and rigid relationship: http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2d8f5443-065d-4485-9385-6f0b5fa417da/flexible-and-rigid-relationship?forum=sqlanalysisservices
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support

Dimension usage multiple columns

In the Data source view, it is possible to create a relationship between a fact and dimension with multiple columns. How is this handled in the dimension usage pane? Can I create a dimensions that relates to a fact on multiple columns?
John Schroeder

Yes it is possible to have multi column relationships in SSAS multidimensional.
If you create the relationship in the DSV then when you create the cube the dimensions usage will pick up the columns in the relationship. If the cube already exists - when you add a dimension that has multiple columns in it's key attribute you can pick
which two columns in the fact should be used to link to the dimension.
http://darren.gosbell.com - please mark correct answers

Many to Many relationship betwee dimension and fact tanle

Hello Gurus,
I have a little question about many to many realtionship between fact and dimension table. The situation is as follows.
Consider there is a fact table F1 and two dimension tables D1 and D2. D1 is joined to F1 with 1 to many relationship. D1 is joined to D2 with again one to many relationship ( Note: D1:D2 = 1:N and D1:F1 = 1:N). I am able to model this by merging D1 and D2 into one dimension table in BMM layer by adding them as logical table sources and creating logical table source join. I have built simple reports and the data returnned is fine. However, I would just like to know what could be the drawbacks of such a model.
We have many other dimesions joined to the fact table and users have access to the answers that means they would could what ever report they feel like. Hence, would just like to know in what cases this model could break which means reports would give wrong data because of a many to many relationship between one of the fact and dimension table.
Thanks in advance.

Hello Copter,
Even I had modeled it by reading this link before. In the situation explained by me dimension D1 is doing the job of table Rules ( as explained in link). The model is fine.
However, my point is to undersatnd in which scenerios this model will break. As already explained, the fact table is joined to various other dimensions, there could be situations in which users select columns from various dimensions and facts randomly.
Hence, which are the scenerios where I might get erroneous counts of meassures. Further, if someone feels this model is correct and would not break in any scenerio then please reply.

Fact and dimension table relationship?

hi
in se38 i executed this program sap_infocube_designs
i got all cubes and percentage , this is directly fact and dimension table relationship based on this i need to take action is it line item dimension or high cardinality (dimen>20% fact line, dimen>10<20 fact is high cardinality.
regards
suneel.

hi,
line item has to be choosen in such a way to control the dim table size for the char that have almost large unique records.
Line item dim table will not be shown by this program.
Ramesh

Column missing in measure group columns list for dimension usage

I added some new columns (dimension ids) to my fact table and refreshed the data source view. Now the new columns show up in the data source view for this fact table. But when I go to dimension usage to tie the new dimensions to this measure, I am not able
to find the columns just added in the measure group columns list.
What do I have to do to be able to see my new columns in this list so that I can update dimension usage.
Thanks.

Hi kvd123,
According to your description, you add columns in fact table and the data source view is already refreshed. However, in dimension usage the meta data is not refreshed. Right?
In this scenario, I suggest you redeploy your cube. Because in Analysis Services, when we modify the cube, the changes are recorded in xxxxx.cube XML file. After you redeploy the cube, those changes are copied to Analysis Services server. Then
the source data will reload into the measure groups.
If you have any question, please feel free to ask.
Simon Hou
TechNet Community Support

What is the logical use of defining Dimension Object Relationships in DBI?

Hi!
I am reading the Oracle Daily Business Intelligence Implementation Guide and as I am following the guide on how to extend DBI, I saw a section which discusses how to create dimension object relationships. Until now, I could not fully realize what is the logical use of defining this relationship among dimension objects. I hope someone can enlighten me on this matter...
Thanks.

It LIVES ON FOREVER, and starts to take on its own personality, hungrily chasing down other objects in memory and ATTACKING THEM AT WILL. Also it grows over time, in its evil attempt to CONSUME YOUR ENTIRE MACHINE, and comes out and EATS YOU UP TOO! MWAHHHAAAHHHAAAA
No wait, that was a sci-fi. It just lives until no more references to it exist and thus becomes eligible for garbage collection, and is only a "JAVA" feature not JDBC.

AMO to extract dimension usage information

Hi,
I am trying to get the details of the key on the fact that join to a dimension using the dimension usage NOT the dsv. I've seen the printer friendly dimension usage produce the answer so I am assuming I can get it. Every time I drill down a measure group I always end up getting the attribute key for the dimension.
I would have thought that this would get me to the tableID and columnID in the xmla in the cube:
Code Block_ocube.MeasureGroups[0].Dimensions[0].CubeDimension.Attributes[0].Attribute.KeyColumns[0].Source
as the xmla looks like:
Code Block
<MeasureGroups>
<MeasureGroup dwd:design-time-name="785ef530-8ab0-449e-b909-19561eb17a7e">
...<Dimensions>...
<Dimension xsi:type="RegularMeasureGroupDimension" dwd:design-time-name="e941d609-3a0e-4dd3-af38-99fd8d31c7ca">
<CubeDimensionID>Small Date</CubeDimensionID>
<Attributes>
<Attribute dwd:design-time-name="ce664bae-a9a3-4f77-b2f2-04f0c18e2960">
<AttributeID>DATE_KEY</AttributeID>
<KeyColumns>
<KeyColumn dwd:design-time-name="1978bf6b-13c8-4085-9125-ab368cd0d71a">
<DataType>Integer</DataType>
<DataSize>-1</DataSize>
<Source xsi:type="ColumnBinding" dwd:design-time-name="3f763005-6a4f-4462-9f83-20a7f4a1c4e5">
<TableID>IIP_MART_DAILY_SALES_FACT_V</TableID>
<ColumnID>TPNM_PROPOSED_START_DATE_KEY</ColumnID>
</Source>
Any help would be gratefully received, as i have been going around in cycles for hours now
Many thanks
Matt

Found the answer, thanks to the guys who produced BIDS Helper
http://www.codeplex.com/bidshelper
I looked at the code for the PrinterFriendlyDimensionUsage class and I found out how to get what I wanted. So many thanks to all those invovled in that.
Code Block
foreach (MeasureGroup mg in _ocube.MeasureGroups)
foreach (MeasureGroupDimension mgdim in mg.Dimensions)
if (mgdim is ManyToManyMeasureGroupDimension || mgdim is DataMiningMeasureGroupDimension || mgdim is DegenerateMeasureGroupDimension)
//call attribute usage stuff
else if (mgdim is ReferenceMeasureGroupDimension)
//call attribute usage stuff
else if (mgdim is RegularMeasureGroupDimension)
RegularMeasureGroupDimension regMDdim = (RegularMeasureGroupDimension)mgdim;
foreach (MeasureGroupAttribute mga in regMDdim.Attributes)
//gets the dimension info
foreach (DataItem di in mga.Attribute.KeyColumns)
string tableid = ((ColumnBinding)di.Source).TableID;
string columnid = ((ColumnBinding)di.Source).ColumnID;
//gets the fact table info
foreach (DataItem di3 in mga.KeyColumns)
string tableid = ((ColumnBinding)di3.Source).TableID;
string columnid = ((ColumnBinding)di3.Source).ColumnID;
//call attribute usage stuff
Matt

Usage of Reference Dimension

Hi,
When I create a new dimension, I was asked to select a Reference Dimension. I search the Admin Guide but I cannot find any explanation on it? Why is it needed? And how can I take the greatest advantage from it when I'm implementing a budgeting solution.
Thanks!
Sunny
Edited by: Sunny Im on Jan 17, 2009 12:15 PM

You want to use this option when you would like to validate a dimension (property of dimension) function by other dimension.
For example for Entity you can use like reference dimension Input Currency.
That's means into Entity dimension you will have a property 'Currency" which can not be removed.
This property has to be filled with a valid currency from dimension Input Currency when you add a new member into entity.
If you will not do that when you will validate dimension you will receive an error that property currency is not a valid member from Input Currency dimension.
In this way you are forcing the user to fill with the right value that specific property for dimension entity.
This is an example but of course the important is the idea. You will be able to get after that what is the refernce for each cross reference.
Regards
Sorin Radulescu

How to create the relationship between ESSBASE 11 and DM in OBIEE11

Hi Experts,
I have one requirement that there is one property table named 'Store Master' in DW,and it contains a lot of attribute, such as Open Date, Close Date, IS 24 Hour etc.
But another data source is essbase and based on this source, I create all reports.
In ESSBASE, it has one dimension and hierarchy Location, and it has four level, Country(L1),Region (L2),Province(L3),Store(L4)
So I want to know how to create the relationship between Location (ESSBASE) and Store Master (DM).
I try to create one relationship in physical layer between Gen4,Location and Store, then drag the open date and close date into Location Dimension in BMM,then Presentation Layer.
When I drag column 'Open Date' ,'Gen4,Location ' and 'Sales' into reports, it will generate the following error message:
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14020] None of the fact tables are compatible with the query request Dim Region.Store Open Date. (HY000)
However, when I remove the column 'Open Date'. it will be ok.
So what I missing the steps? Please help me. Thanks.

>
'2. Now, pull the 'Store' column from relational DB onto the Gen5, Location column from Essbase. This action now creates, two logical sources for your 'Store' column.'
If the length from different data source is not same,such as 1001(DM),L_1001(ESSBASE), can I drag the 'Store' column from relational DB onto the Gen5, Location column from Essbase?
I think it does not work.Right?Hi,
I am not sure if you are talking about the length(as in varchar(128)) of the member value being different in different sources, or the member itself is different in both the sources.
I am still assuming, that you are referring to the members not same in both the sources.If it is, the whole concept of federation is based on conforming dimensions. So, it needs that the same dimension information is present in both the sources and then only, you know we can analyze the numbers based on this dimension. So, either the dimension being different in both sources, or the members not present in both the dimensions might lead to incorrect numbers.
So I select Store Attributes in relation DB and Location in ESSBASE in physical layer, then create the physical join, such as right("Hour Sales"."H_Sales".""."H_Sales"."Gen6,Location",4) = "Authorization".""."EDW"."T_EDW_MDM_STORE"."US_CODE", then drag the OPEN_DATE and CLOSE_DATE in relation DB to Location in ESSBASE in BMM,finially drag them into presentation layer.We create physical layer relationships, to send over the same relation to the underlying database during querying. So, creating a physical relationship between essbase cube and relation database would not help here.
When you set up this federation, BI Server sends individual queries to each source and maps the conforming dimension members internally.
Hope I was clear, and this helps.
Thank you,
Dhar

Dimension usage relationship between dimensions

Similar Messages

Maybe you are looking for