- For individual users
- Instant access to solutions
- Ask your tech questions
- Start your 30-day Free Trial
Main Topics
Browse All TopicsIn Cognos 8 Framework Manager, I have 2 views - the database view and the business view. I do NOT want to rename any fields in my database view, so I will always merge into a query subject before any table makes it to the Business View.
If I merge a table that has relationships into a new Query Subject for the Business view, Cognos will ask if I want to "Recreate these relationships" in the merged query subject.
If I select "Yes", it will create another relationship object, such that there are now 2 relationships - one with the original database view item and one with the new merged query subject item.
If I select "No", it will not create another relationship object, but the underlying relationship still exists, because the new query subject references the database view table, which has a relationship.
My question is this: Why does it matter? Why would I want to select Yes or No? If the relationship is underlying, what is the benefit of recreating it, and having two relationship objects?
I ask because I would rather NOT have relationships in my Business View unless there is a good reason to - this is just too confusing. I'd rather keep all relationships in the database view. Please advise/
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: James_JnrPosted on 2009-11-04 at 00:50:45ID: 25737467
There are reason why you would want to do this, but it all depends on what you are trying to achieve in the model.
An IBM consultant told me that you would not bring them into the business view as all relationships should stay in the DB view, this makes sense from a Data Modelling perspective. I think the answer you are looking for is this;
In the model I am currently building we have a OLTP database and not a DW underneath. We are creating a DMR to sit on top of this to mimic a DW. In order to get the results I need I have to model out traps and create standalone subjects that give me the results I want, But I need these to be related to other subjects but not just through the underlying relationships but to other query subjects. So if you create a merged Customer,Customer Details table without bringing in the underlying relationships you have a standalone subject. If you then manually create a relationship to say Customer Sales, when you run a query involving both, Cognos will first retrieve the results of the Customer,Customer Details then join them to the results of Customer Sales on the relationship you created. If you had brought in the underlying relationships you might have had a relationship from another table joined to say customer that would interfere with the results you are after.
It is a confusing area I must admit, but I have found it to be useful for getting around issues with the data not being stored in the way you want to see it.
Hope that helps, James