Hi,
i've setup a MDW layer with proper relations between tables. At this point I wanted to create a relation diagriam to visualise to my client the relation between his entities.
my tool of choice was SQL Management Studio. Only then i've realised that TimeXtender only create DW_Id as physical primary key and the relations between tables are managed internally
Is there a way in TimeXtender to visualize the relations between the tables?
I've already put my vote here
Best answer by JTreadwell
Hi Dror,
Thanks for your post.
Alternatively you can set the relationship type to "Error with Physical Relation". This will create a physical foreign key in the database. Then you can use SQL server or a 3rd party tool to visualize the data model. The downside of this approach is (and this applies to all SQL foreign keys) it will discard all results in the table without a matching value in the related table. So you will need to implement an "unknown member" in dimension tables to handle this occurrence.
Hope that helps.
Hi Dror, I am sure you know that if you choose the Fact table(s) of your data model in TimeXtender and you select Visualization->Relation Diagram you can see a graphical view of relations between fact and dimensions based on relations you selected in MDW. It is not anyway a complete DWH view, that I guess is your request :)
Hi Andrea,
Yes, I'm aware of that feature. I have several fact tables in my model and i would love to see the interactions between all of them (on layer perspective as oppose to table perspective)
+5Hi Dror,
Thanks for your post.
Alternatively you can set the relationship type to "Error with Physical Relation". This will create a physical foreign key in the database. Then you can use SQL server or a 3rd party tool to visualize the data model. The downside of this approach is (and this applies to all SQL foreign keys) it will discard all results in the table without a matching value in the related table. So you will need to implement an "unknown member" in dimension tables to handle this occurrence.
Hope that helps.
Hi Joseph,
Sounds good. Unfortunately it's not working for me. I'm getting the following error:
Physical relation error(s):
The relation organizations_organizationId must be a unique index on the primary field organizationId.
What am I doing wrong?
+5Hi Dror, This is likely due to creating the relation in the wrong direction. In TimeXtender, relations should be created by dragging from the "one" the the "many" of a one-to-many relationship.
Hi Joseph,
The relation direction are properly configured (from one to many).
Table primary key remains to be 'DW_Id '
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
