Skip to Content

OK to have unrelated tables in same universe?

We have a database that has a series of unrelated tables. Is it bad idea to have those unrelated tables in the same universe?


Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Nov 05, 2015 at 10:53 PM


    Yes,It's not a good practice or i can say bad design.If you are going to put the unrelated tables then users must know which objects they have to select creating objects and when they will get the errors or wrong result.

    This approach is more based on the limited users community and they should know how this will work.If users doesn't know i would suggest don't go for this approach.

    In one of my project we went for this approach but in that case users were used to with this approach and they forced to go with this.


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Noel Scheaffer

      Rather than use contexts for this, use aggregate navigation. It's not what aggregate navigation was designed for but it's something that I've used it for in the past. Typically you'd use it in an OLTP schema. As Amit says, you wouldn't generally put disparate tables in the same universe but it can often be the case that the same target audience would need them both.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.