Logical Model Preferences - Please clarify

I need an example to help me understand the Relation Cardinality option here
Say Entity A and Entity B are in the logical model. Entity A has a primary Key that acts as the foreign Key in Entity B.
Source Optional: Controls whether the source entity in a relationship must, by default, contain one or more instances. If this option is enabled, source instances are not required for all relationship types; if this option is disabled, one or more source instances are required for all relationship types.
Target Optional: Controls whether the target entity in a relationship must, by default, contain one or more instances. If this option is enabled, target instances are not required for all relationship types; if this option is disabled, one or more target instances are required for all relationship types.
- What is the source here? Entity A? and Entity B is the target.
- Please confirm if the following understanding is right? by converting it to outer join between Entity A and Entity B.
Source Optional Target Optional Result (Source to Target cardinality)
Checked Checked 0,1,n -> 0,1,n
Checked Unchecked 0,1,n -> 1,n
Unchecked Checked 1,n -> 0,1,n
Unchecked Unchecked 1,n -> 1,n
- Do these options affect the way the on delete option is chosen in the relational /physical model?
Thanks & Regards
Tiji

What is the source here? Entity A? and Entity B is the target.This is initial staging for created relationship if you first click on A and then click on B. "Source" and "Target" itself doesn't have additional semantic. Important are cardinality settings - they define parent and child entity. You can change source and target in relationship dialog and if you set properly cardinality you'll get the same result.
... OptionalOptional means that related end of relationship can exists on its own, otherwise it's in the context of other entity. Delete rule is set to "set null" during transformation to relational model when child entity is optional.
Also you can check Re: Relation Properties - Cardinality - "Identifying" vs. "Target Optional"
by converting it to outer join between Entity A and Entity B.I don't catch it - can you elaborate?
Philip

Similar Messages

  • Difference between OBIEE Logical Modelling and physical modelling

    HI.
    what is the difference between logical modeling (BMM) and physical modelling(Physical layer) in obiee admin tool
    please narrate it in definition format
    thank you
    rakesh

    Hi rakesh,
    Administrator tool consists of 3 layers
    Physcial layer:-It is typically first layer built in the repository.Contains objects representing the physical data sources to which the BI server submits queries.It may conatin multiple data sources.The common way is to import metadat from different databases.You can define joins after import if they are not defined.
    Business model and mapping layer:-It is defined as business or logical models of data and specifies the mapping between the physical and business layers.This is where the physical schemas are simplified to form the basis for the end user.We can say data is seperated into facts and dimension tables
    Presentation layer:-simplifies and organizes the business model to make it easy for users to understand and query
    go through the user guides for all the definition and subject
    Hope it helps you.my points?
    By,
    Kranthi
    Edited by: Kranthi.K on Sep 1, 2009 10:22 PM

  • Logical model fwd engineer to relational model.  Missing FK relationships

    We are experiencing missing relationships in the relational model when engineering from logical model to the relational model. The logical model objects have properly defined primary keys defined. We are using SQL Data Modeler v3.1.700. Any suggestions on how to engineering these relationships without deleting the objects from the relational model.
    Thanks,
    Ed

    Hi Ed,
    I presume you had some relationships in the Logical Model that you were expecting to be engineered to Foreign Key relationships in the Relational Model.
    Please can you provide more detail to help resolve your problem. For example:
    Was the problem on an initial engineer from the logical model? Or on a re-engineer?
    Are you using Entity subtyping in your Logical Model?
    Are there any relevant error messages in the log file? (This is normally file datamodeler.log in folder datamodeler\datamodeler\log.)
    David

  • Q:  Data Modeler - Logical Model - 0 or 1 to....relationships...

    Hi,
    I’m currently at a client where we’re using Oracle SQL Developer Data Modeler to design our Logical Data Models (as part of an overall deliverable).
    When in the Oracle SQL Developer Data Modeler (in the logical view), I’m trying to figure out if the tool has the ability to create a “zero or one to” relationship between entities.
    According to the relationship options available, it only seems to show:
    One to One,
    One to Many (*),
    Many (*) to One, or
    Many (*) to Many (*)
    In the preferences – Data Modeler – Diagram – Logical Model, the notation type is set to “Barker”.
    I don’t see anywhere else where configuration can affect the variation of these options…
    Is there a way to show either a “Zero or One to…” relationship between entities?
    I’ve also loaded version 3.1 (beta) and it appears to be behaving the same as 3.0…
    Any insights are greatly appreciated…
    Thanks,
    Patrick

    Hi Kent,
    When I looked at this option, I was expecting to see a "|" and/or "O" in front of the crow's feet. I was not expecting to see a dashed line. Now I know...
    Thanks for your reply.
    Regards,
    Patrick

  • Unable to generate Logical Model Diagrams through Reverse Engineering

    Hi,
    I am currently using SQL Developer Data Modeler Version-3.0.04.
    I have generated Logical Model Diagrams from Relational Model Diagrams through Reverse Engineering (Done by pressing an" engineer to Logical Model button" on top panel of sql developer) .I saved the DMD file (source file) once i had done generating the logical diagrams.Now if i reopen the DMD and open the logical diagram again I found that most of the tables had lost their relationships.So i tried to regenerate the Logical Model Diagram again from the same Relational Diagram but it is not being generated unless i create a new Relational Diagram.Is there a way to generate multiple Logical Diagrams for the same Relational Diagram rather than creating a new one for each Logical Diagram to be created.
    Regards .
    Thanks in advance.

    Any comments on this issue?. Please let us know.

  • Engineer to Logical Model is not working!

    Hello
    I have a model that I started by reverse engineering from the database and generated the ER Diagram by reverse engineering to Logical.
    After this I had to add some more tables to the relational model which I realized was already in the database and reverse engineered that into the model as well. Now, I am unable to Engineer to logical. Is this an expected behaviour as designed?
    Next I am going to try to reverse engineer from a relational model to a blank logical in a new data modeler design file. After that I will merge that change into current model. Please let me know if there is an easier way around this.
    Thanks & Regards
    Tiji

    The valid scripts in this post solved my problem.
    Re: Switch from v3EA4 to v3.0.0.4 production - Corrupted models?
    Script #1: Search for invalid mappings.
    Script #2: Clean up by removing invalid mappings.
    Script #3: Call Forward Engineer dialog with exception handling included to share with forum or debug.
    Script #4: Call Reverse Engineer dialog with exception handling included to share with forum or debug.
    After running Script #2, when we run Script #1, the log will be empty which is the expected result. Now my reverse engineering option does work from relational to logical.
    Thank you Phillip and DMBee for guiding me to the solution.
    Thanks & Regards
    Tiji
    Edited by: Tiji on Jun 14, 2011 8:31 AM

  • SQL Data Modeler - Problem Opening Saved Logical Model

    I created a logical model in the Data Modeler tool and saved it as a .dmd file.
    When I try to open the .dmd file nothing pulls up. I get the following logs:
    2012-11-08 11:09:45 - Building Diagrams
    2012-11-08 11:11:25 - Open Design: 'CTS'
    2012-11-08 11:11:25 - Open Design: 'OK'
    I created a test model and saved it as a .dmdz file and I get can it to open. I tried to revise the file type of my original model to .dmdz and when I try to open, I get the following error message and nothing shows up.
    "Some objects are not loaded correctly. See the log file for details." There is nothing in the log file.
    Any ideas about how to get my .dmd file to open correctly?

    What worked for me was going to Tools .. Preferences .. Data Modeler, and then making sure that each of the "Default <x> Directory" specifications pointed to a part of the hard drive that my operating system login user had permission to reach. (I suggest a sub-directory under your login user's "My Documents" or "Documents" folder, or whatever your operating system calls it.) Allowing the initially blank defaults produced weird behavior on my machine. YMMV.
    Mark

  • Delete Rules between Logical Model and Relational Model are different

    Relation Properties in Logical model has three Delete Rules: "RESTRICT", "NO_ACTION", "SET NULL".
    1. "RESTRICT" and "NO_ACTION" are same
    2. "CASCADE" is missing.
    However, Foreign Key Properties in Physical model has three Delete Rules: "RESTRICT", "NO_ACTION", "CASCADE".
    1. "RESTRICT" and "NO_ACTION" are same
    2. "SET NULL" is missing in this case.
    They are supposed to have "NO_ACTION or RESTRICT", "SET NULL", and "CASCADE".
    Please fix this ASAP. It is really annoying in Engineering process. Modeler creates duplicate wrong relationships while it engineers.
    Thanks.
    Edited by: hayangae on Oct 9, 2012 1:01 PM
    Edited by: hayangae on Apr 3, 2013 4:08 PM

    Hi,
    it seems you are not using the latest version 3.3. In earlier versions - delete rule set on relationship was used only in some cases to set delete rule on related foreign key. Now delete rule is transferred to FK as it's defined on relationship.
    I assume you are using Oracle database - "Restrict" doesn't appear anymore for Oracle.
    2. "SET NULL" is missing in this case.Most likely the foreign key is set as mandatory thus you cannot use "set null" as option.
    Modeler creates duplicate wrong relationships while it engineers.Can you elaborate on that - example?
    Philip

  • Logical model cannot refer to 'remote objects'?

    Hi
    Using DM 3.3.0.747.
    In the relational model one can drag and drop in a table from another relational model from a separate design.  This shows that table as a linked table and can be refreshed via the 'Synchronize Remote Objects' and allows that table to be referenced from your 'local' tables (i.e. used in foreign keys).
    I tried the same, but for a logical model entity.  This does not work/is not allowed?  What is the expected behaviour?
    We would like to use this for logical models as well.  (So that we may develop/document the logical models separate, but use common/shared entities in the same way possible in relational models.  This will help us a lot in keeping the models smaller and easier to manage and version control.)
    Thank you & Regards

    Hi Ed,
    I presume you had some relationships in the Logical Model that you were expecting to be engineered to Foreign Key relationships in the Relational Model.
    Please can you provide more detail to help resolve your problem. For example:
    Was the problem on an initial engineer from the logical model? Or on a re-engineer?
    Are you using Entity subtyping in your Logical Model?
    Are there any relevant error messages in the log file? (This is normally file datamodeler.log in folder datamodeler\datamodeler\log.)
    David

  • DataModeler: Cannot engineer from logical model to relational model

    Hello,
    I have been trying for a couple of (very frustrating) hours to engineer a very simple logical model to its relational model. The toolbar button (and also menu option) that should do this just does nothing. No errors, no feedback, absolutely nothing!!! However I could engineer a relational model back to its logical model.
    I am using SQL Modeler version 1.5.1 build 525 on Windows Vista. I have closed and restarted the program many times but to no avail. Are there other factors (e.g. anti-virus, JDK etc) that could be responsible? But then why are other parts of the software working but not this one?
    Please kindly send your advice asap so I can proceed. I really like the Modeler and will not want to discard it.
    Thanks,
    Chiedu

    Hi Folks,
    I was able to figure out the likely cause of the problem. The version of Modeler (datamodeling-1.5.1-525-no-jre.zip) I used was downloaded without JRE. The current version of JRE installed on my computer is Java 6 Update 12 (build 1.6.0_12-b04). I suppose the two don't quite work very well together.
    I have now downloaded and installed another version (datamodeling-1.5.1-525.zip) with its own JRE and the problem was resolved.
    My guess is that the problem was due to the incompatibilities that may exist between Data Modeler and the various versions of JRE.
    Thanks.

  • Engineer between Logical Model and Relational Model

    I am trying to update changes from one model to the other but there are dublicate entries generated instead of updates.
    The Logical Model was imported from Oracle Designer, the Relational Model was imported from data dictionary.
    Our rule is, that the name of Entities/Tables and Attribute/Columns are identical.
    So I changed the Naming Standard of the Logical Model in Preferences
    from Separator = Space to Separator = Character with char = Underline.
    If the entity is not existing, it is created with the correct name.
    If the entity exists, a new entity is created with Namev1.
    The same happens when I try to update changes in the other direction.
    How can I achieve that the existing entity (or table) is updated and not a new one is created?
    Or in other words, is there a way to link entities to corresponding tables?
    Walter

    Hi Walter,
    The Logical Model was imported from Oracle Designer, the Relational Model was imported from data dictionaryit's good to import entities and related tables from Designer repository together. Data Modeler will import the link between them and use that link in synchronization between logical and relational model. After that you can import details for physical model from database.
    If you don't have tables in Designer repository and keep the same names for entities, attributes, tables and columns then you can engineer logical model to relational and import details from database.
    Philip

  • How to change "Relation UID" attribute name in logical model?

    Beginner question here, sorry if it has been covered already.
    In the Logical model in Data Modeler, how do I change an attribute name which is used as a "Relation UID"?
    For example, I create two entities each with a Primary UID called "id", then create a 1:1 relationship. Each entity will now have an attribute called "id1" marked as a Relation UID, but I can find no way to change the attribute's name. Is there a way?
    Thanks.

    Hi GuyM,
    you need to check setting in preferences - "Data Modeler>Model>logical" - FK attribute name synchronization - clear the check box if you want to set the name manually.
    Philip

  • User Authentication Logical Model DB2

    Hi Im attaching a logical model. Experts please take a look an guide for changes or to include more details. This is basically a user authentication logical model ERD
    Eagerly awaiting your reply. I am unable to attach a file if i can share the file it willl be easier... please tell me how to attach a word file .
    Thanks
    Organization
    OrgId PK
    LocId FK Location
    ClientId FK Clients
    Org Desc
    Org Location
    Create Date
    Last Updated By
    Location
    LocId PK
    Loc Desc
    Address
    Create Date
    Last Updated By
    Update Date
    Clients
    ClientID PK
    ClientName
    Department
    DeptId PK
    ClientID FK Clients
    UserId FK Users
    BookId FK
    DeptName
    Location
    Create Date
    Last Updated By
    Update Date
    USERS
    UserId PK
    Password :
    User_Role_Id FK Roles/Grps
    OrgId FK Organization
    Effective Dt
    Status
    Create Date
    Last Updated By
    Update Date
    User Roles ( Groups )
    User_Role Id PK
    UserId FK USERS
    BookId Fk Book_Types
    Role Id FK Roles
    Group Desc
    Create Date
    Last Updated By
    Update Date
    Roles
    Role Id PK
    Role Name
    Create Date
    Last Updated By
    Update Date
    BookTypes
    BookId PK
    BookType
    Create Date
    Last Updated By
    Update Date
    USER_Details
    UserId FK USERS
    DeptId FK Department
    Force Password Change Days
    Secret Question
    User Phone
    User Address
    DOB
    User Email
    User Mobile
    User Status
    User Supervisor
    Last Updated By

    Thanks for your reply Yusef.
    I am actually creating an ERD for authenticating the user when he logs into the database. So I will need a set of tables to identify if user exis and password is correct.
    After this some tables will exist for checking his department, his group. On the basis of his group he will be able to access only relevant parts of application. Its like a role or a privelege thing.
    Please tell me if the database tables that I have identified are correct ? Please ask questions so I may get to the best solution please.
    Thanks

  • User Authentication Logical Model

    Hi Im attaching a logical model. Experts please take a look an guide for changes or to include more details. This is basically a user authentication logical model ERD
    Eagerly awaiting your reply. I am unable to attach a file if i can share the file it willl be easier... please tell me how to attach a word file .
    Thanks
    Organization
    OrgId PK
    LocId FK Location
    ClientId FK Clients
    Org Desc
    Org Location
    Create Date
    Last Updated By
    Location
    LocId PK
    Loc Desc
    Address
    Create Date
    Last Updated By
    Update Date
    Clients
    ClientID PK
    ClientName
    Department
    DeptId PK
    ClientID FK Clients
    UserId FK Users
    BookId FK
    DeptName
    Location
    Create Date
    Last Updated By
    Update Date
    USERS
    UserId PK
    Password :
    User_Role_Id FK Roles/Grps
    OrgId FK Organization
    Effective Dt
    Status
    Create Date
    Last Updated By
    Update Date
    User Roles ( Groups )
    User_Role Id PK
    UserId FK USERS
    BookId Fk Book_Types
    Role Id FK Roles
    Group Desc
    Create Date
    Last Updated By
    Update Date
    Roles
    Role Id PK
    Role Name
    Create Date
    Last Updated By
    Update Date
    BookTypes
    BookId PK
    BookType
    Create Date
    Last Updated By
    Update Date
    USER_Details
    UserId FK USERS
    DeptId FK Department
    Force Password Change Days
    Secret Question
    User Phone
    User Address
    DOB
    User Email
    User Mobile
    User Status
    User Supervisor
    Last Updated By

    You posted this in three different forums!
    Can you explain why.
    Also you seem never ever to mark a question as resolved.
    That is the rude behavior of most newbies here, but then that has to be stopped.
    I'm hard pressed to see whether this model is correct. It is very unlikely a client can have multiple organizations and multiple departments. Likely you erroneously reversed those relationship.
    Also the FK relationship between users and books is almost certainy incorrect, as in the users description you refer to booktypes, which appears to be a fk to the book entity.
    You should redo this design and come up with something better. This one is not correct at all.
    Also you should refrain from cross- and multiposting.
    Sybrand Bakker
    Senior Oracle DBA

  • Logical Model Naming Standard (Title Case) and Foward ENGINEERING how to???

    Hi,
    I just installed the datamodeler v3.3.0.747.
    I want to use the Title Case style as separator style in my logic Model... To do this, i go to the Preferences Settings (Tools > Preferences > Naming Starndard > Logic Model) and set the Title Case as separator Style...
    However, when i do foward engineering of the logical model... The Style is omitted and everything is like the logical model... For example,
    If i create an entity called: ManagedAccount, i will expected that when i do fwd enginnering, the table associated to that entity will be call as Managed_Account; However, i still getting ManagedAccount...
    So, What am i doing wrong??? or this is a bug???
    Thanks!

    Hi,
    in order to get it working in current release you need to create glossary even empty one and set its property "Incomplete Modifiers" to true (check the check box with that name), and to to add that glossary in "Tools>Preferences>Data Modeler>Naming Standard".
    We'll change it in next release to work without glossary for this particular case.
    Philip

Maybe you are looking for