It's adding same column to relational model over and over

I'm using 3.3.0.747 now, and I'm pretty sure that it wasn't doing this when I was using 3.1.4. I go into the logical model and add an attribute (say "My notes") to an existing entity (say "Specifications"), adding a preferred abbreviation of "notes" to it. I engineer to the logical model, and it dutifully says that it's going to add a column to the corresponding table ("specs"). And it does.
Now, later, I add some attributes to some other table. When I do the engineering, it says that "notes" doesn't exist in "specs" and it's going to add it. If I let the engineering go through, I find that the relational model for "specs" now has two columns on it, "notes" and "notes1". If I do it again, I get "notes2". If I delete "notes1" and "notes2" and engineer again, "notes1" comes back.
I'm not finding that it does it this every time, but it's doing it for maybe half the columns I add to existing tables. (I haven't figured out a pattern.) If it happens to be a foreign key relationship, it creates an additional foreign key.
So far I've just added a step to my process to hunt down the new columns and delete them (or flag the logical model to not engineer the table at all if I know I haven't changed anything), but there must be something obvious I'm missing..
Edited by: dbomp on Apr 17, 2013 10:53 AM
I'll take back one thing I said: If the once-new column is related to a foreign key, it does keep re-creating the column, but it doesn't create new foreign key relationships to go with it.

I figured it out so I thought I'd put this here in case others bump into it.
What's going on is that the logical-to-relational engineering comparison tool doesn't recognize relational columns that the engineering tool didn't create.  Sometimes I would add columns to both the logical and relational models manually rather than engineering.  Say all I wanted to do was to add an active_flag to a table.  I'd add it to the relational model and then add it to the logical model's corresponding entity with exactly the same values.  Later, when I had a bunch of logical model changes to engineer, it wouldn't recognize the active_flag ("preferred abbreviation") in the entity as being the same thing as the active_flag in the relational table, and it'd create an active_flag2 column.
Lesson:  only create new relational table columns by engineering them from the logical model.

Similar Messages

  • Adding new Fields In Relational Model

    Hi ,
    I am brand new to the world of data modeling as well to Oracle SQL Developer DM. I am currently using version 3.0.0.665 of the data modeler. While doing the data modeling there are tables that get the data from UI screens and then there are tables which store processed data (think of them as summary tables from DWH).
    My requirement is that for the UI linked tables I need standard set of columns in relational model but I don't want to add them in my logical model as these are just technical columns. To elaborate consider this employee details screen.
    UI Screen Elements:-
    Employee Name
    Department Name
    Manager
    Salary.
    To store data from this screen I create a logical model with only 4 attributes to map my UI screen elements. In my relational model though I would need employee_id, department_id, manager_id which are not part of my UI elements. Apart from this specific requirement for employee table I have a generic requirement for all UI screen linked tables to capture the create date, create id, create screen, version number, update date, update screen and another column called deleted to indicate if the record is logically deleted or not. These additional 8 columns are not part of the logical design and should be present only in the relational domain that too for UI linked tables only.
    Any inputs in helping me out with understanding how to implement this would be greatly appreciated.
    Thanks and Regards
    Sagi

    You sound like you need to read up on entity relationship modeling first (start with Wikipedia). Also check out the SDDM videos on the Oracle site (http://www.oracle.com/technetwork/developer-tools/datamodeler/overview/index.html), and walk throught he tutorial that comes with SDDM. Logical models are not really for documenting fields that appear on a screen. It goes way beyond that.

  • Engineering to and from logical and relational models

    I have tried to modify a logical model entity by adding an attribute or two, tried to engineer to the associated relational model, only to have the engineering process create a brand new table rather than adding the new column or two to the existing table.
    Creating the column in the table first and engineering back to the logical model didn't appear to do anything, although I might have missed a new logical entity.
    Is this how the product is supposed to work?

    Hello,
    I'm sorry but your steps are not evident for me.How it works - you can start from table or entity, it doesn't matter which one is first you should be able to synchronize changes.
    Let's assume you have two relational models RM1 and RM2 and table TABLE_1 in RM1. if you engineer RM1 to logical model then entity will be created that corresponds to TABLE_1 in RM1 (and it will be named TABLE_1 if you don't use glossary that provides replacement of TABLE with something else).
    You can add attribute to entity and engineer logical model to other relational model (RM2) - new table will be created in RM2.
    Add one more attribute to entity and engineer to RM1 - two attributes will appear showing that two new columns can be created - they are not selected and you have to select them if you want columns to be created.
    You'll get only one new attribute (column) if you engineer to RM2 - the first added attributed is already there as column.
    Of course you can add columns in tables and can synchronize them with entity in logical model.
    Philip

  • SSIS 2005 Adding a Column to an existing Package

    Hello Forum
    forgive me but it 's been over 5 years since I touched SSIS.
    We have an SSIS package that compiles data and then exports the data to a MS Ecxel Spreadsheet.  We are struggling to add an existing column.
    Essentially the package reads data from source, performs a "Data Conversion" so that the Output Columns are named "Output of Field1" etc and then the data is exported to the Excel Spreadsheet.
    The developer has succeeded in adding the column to the Data conversion and has manually added the column in the Spreadsheet; however although the converted column appears in the Column Mappings, the corresponding destination Column in the Spreadsheet does
    not.
    Can someone please provide instructions on how we can achieve this?  Many thanks.
    Please click "Mark As Answer" if my post helped. Tony C.

    You have to re-configure whole data-flow task inside your package, where ever your new column effected in package.
    Thanks
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Crystal Reports XI - How to pull same column value with different select...

    I have a report with many (around 30) sub reports and it is giving serious performance issue. I am currently finding out a strategy to improve the performance. I see that most of the sub reports are taking same parameters from main report except for one parameter which is different for each sub report and hard coded in them and pulling up the same column value from a oracle database with a different select criterion. I am trying to find out a way using either of command/crystal formula/SQL expression which can do the same job for me and give me performance improvement. I tried to take the parameters from the main report in one sub report and mapped them to parameters being transferred to the command and then drag and drop the field for which I need to display the value but due to some reason it is not returning values when I am trying multiple commands...I need some help in selecting a strategy for this issue resolution and some guidance....Any help would be highly appreciated....

    My version is 11.5.8.826. First of all I need to make it clear that I have 6 set of sub reports and each set has 5 sub reports. So if I can resolve the issue for one set, I resolve it for all. The sub reports are doing nothing but fetching a column value using a simple SQL SELECT query and appending to the right of a box in main report. The issue is that all these queries embedded into the sub reports are using same SQL except for one parameter in the "where" clause and they are fetching same column value from the database and fortunately all of them are returning same number of results. So at the end these results create a table when run. The only way I can stop using sub reports is by creating a table in the main report and use some object(formula/command/SQL expression or whatever) to fetch that column value using the same filter conditions. But please take a note that I need to use and append the same column value from a database table and use different filter conditions and append them to the right so that at the end they create a table...as long as I get the table in the output with a decent performance , anyone will be least bothered about what I used inside the report.....please ask me as many questions to get more lights on the issue....

  • Where is the documentation for Oracle Spatial Relational Model?

    Hi,
    I'm working with Oracle Spatial for my schema model. In the documentation "Oracle Spatial User's Guide and Reference" there is a note about what this is in OTN but i don't find it!!
    Can anybody help me, where I find the "Oracle Spatial Relational Model Guide and Reference"?

    Thanks! But just i have read this information. And in the documentation for spatial 9.0.1 there is one document only, and in this document there is a Note that reference to nonexistent document with title "Oracle Spatial Relational Model Guide and Reference" this is the document that i'm searching.
    Thank you for your help!

  • Column Prefix from Logical to Relational Model

    Hi,
    is there any option, that data modeler append an prefix (table short name) to a column, when the logical model will be transformed to relational model? (Same behavior as Oracle Designer)
    Example:
    Logical Model
    TABLE: PERSON
    TABLE-SHORT: PERS
    COLUMN-1: ID
    COLUMN-1: NAME
    Relational-Model
    TABLE: PERSON
    COLUMN-1: PERS_ID
    COLUMN-2: PERS_NAME
    Kind Regards,
    Stefan

    Thanks for your answer!
    This Script is not really working for me, because of our foreign keys.
    All our Foreign-Keys are named "ID" (for nummeric column) or "INDEX" (for a varchar column). After the transformation form logical to relational all the foreign-keys are named like "ID1", "ID2", "ID3", "INDEX1", "INDEX2" etc.
    There is no way to apply this script before the foreign-keys where added in the tables?
    The Second Way is to create a new script for this task.
    am i the only one with this problem? :-/

  • Synchronizing Column Comments from Relational Model to Data Dictionary?

    I've changed/added column comments to a table in my Relational Model. When I try to sync the changes to the Data Dictionary of the Database the new/changed column comments are never included. I can actually see that the values in the Field "Comment in RDBMS" are different in the Compare Models Preview Window but the line is not highlighted in red as I expect, in fact it is even grayed out. I also can't check the corresponding checkbox "selected".
    Is there a way to get the comments to synchronize? Do I miss any option I have to set first? Ist this a bug or expected behaviour?
    I'm using version 4.0.3 x64 of Data Modeler.
    Any help would be much appreciated,
    Charlie

    Hi Charlie,
    The greying out of the "Comment in RDBMS" property would suggest that you have filtered out this property for Column objects in a previous Compare.
    To unset the filtering, repeat the sync, and when it displays the Compare Models dialog, select the Options tab and then the Properties Filter tab below it.
    Select "Columns" in the left pane, and then find the entry for the "Comment in RDBMS" property in the right pane.  The "Included" check box should be set.
    You can then select the Refresh Trees button below these two panes.
    If you then go back to the Details tab, any differences in the "Comment in RDBMS" property for Columns should now be highlighted in red.
    David

  • SQL Datamodeler: engineer to relational model: column names

    Hello
    Suppose I have an attribute called DAY OF BIRTH. Is there a way I can forward engineer this attribute to a column name DAY_OF_BIRTH?
    (I know you could have a coulmn name "day of birth" but thats not what I want)
    Regards Erik

    Hi Erik,
    1) you should check separator settings in General options>Naming Standard -it should be "space" for Logical model and "underscore" for Relational model;
    2) "Apply name translation" should be selected in engineering dialog
    Best regards,
    Philip

  • Engineer to Relational Model: deleted attributes / undeleted columns

    Hello,
    I am using Datamodeler 3.3.0.744.
    I'm modifying an existing logical model: I'm deleting one or more attributes in an Entity.
    Then I'm executing "Engineer to Relational Model" in oder to get an up to date Relational Model (it existed already).
    The corresponding columns are not deleted in the Relational Model, even though attributes don't exist anymore at the logical level.
    I can't find any option available in order to do that...
    In the previous release (3.1), it worked fine, I could choose the behavior related to the deleted attributes (deleting or not deleting corresponding columns).
    Edited by: user4995029 on 27 mai 2013 02:43

    When your forward engineer for a 2nd time you should see a dialog that has the logical on the left and the relational on the right. Entities that are new or changes have an exclamation point next to them. If you open that you will eventually drill down to see the attribute/columns. Where your dropped an attribute it will say "To drop". The check box is unchecked by default. If you check it then when you forward engineer those should get dropped from the associated table.
    Is it not working that way in 3.3?

  • Adding size to exisitn domain not changing in relational model

    Hi all,
    I defined a domain type of integer without any size. I now know the size and have changed the domain type but the column definitions in the relational model dont have the new size. What am I doing wrong?
    thanks
    Magnus

    Hi Philip,
    once again you are the font of all modeller knowledge, thank you very much
    regards
    Magnus

  • Problem in Adding two buttons under same column header (in JTable)

    Hi,
    I have a JTable and to a particular column i want to add two buttons.
    Here the two buttons should be under the same column header and i need to add listners to these.
    Any idea how to do this?
    Thanks & regards
    Neel

    Of course as your header is drawn by a renderer, the buttons don't actually work, but you can listen for mouse clicks within the area of the header and see which button the mouse position was over.
    See the Java Table Sorter Demo code for how to add a mouse listener to the header...
    http://java.sun.com/docs/books/tutorial/uiswing/components/example-1dot4/index.html#TableSorterDemo
    ....and from there you should be able to determine where in the component the click occured by using the getX() and getY() methods of the MouseEvent to determine which button in the renderer component was clicked. Use something like Rectangle.contains() to match the click location against the buttons.

  • SDDM EA 3.1: Engineer to Relational Model (subtypes)

    It seems that mandatory attributes of entity subtypes become mandatory columns on the corresponding tables even when you engineer to "one table" (the super type).
    In that case I would expect that the column would become optional.
    Even better: a check constraint would verify that the column was not null for records belonging to the originating subtype.
    / Marc de Oliveira

    1) Funny, when I dropped the column, and had it recreated by the engineering process, it worked correctly. But re-engineering the old column kept setting it to mandatory even when I manually set it to optional. I have a sense that some of my objects are ignored by the tool... Only when I drop them and recreate them they seem to be recognized. I had the same issue with some entities that consistenetly did not got engineered into my relational model. Only when I created a new ER-diagram and included the same entities they would get engineered into the relational model...
    2) Designer did this. When a supertype table was generated in the "one table" mode there would always be a new column called SUBTYPE with a constraint allowing the short names of each subtype as values (ex: for the table PARTIES the SUBTYPE column could only contain the values PERS and ORG). With this in place you could create constraints such as "SUBTYPE = 'PERS' and FIRST_NAME is not null or SUBTYPE = 'ORG' and FIRST_NAME is null".
    Regards,
    Marc de Oliveira

  • Fwd engineering entity name changes to relational model?

    I changed an entity name in my logical model after generating a relational model. But, I cannot figure out how to have SDDM (3.0.0.665) propagate this change to the relational model.
    In the Engineer To Relational Model screen, if I select the changed entity from the tree view, in the Details pane there is a "Selected" check box next to the Name property (this line shows the discrepancy between logical name and relational name) but I can't check it. Under the Compare/Copy Options tab in that same dialog, the check box next to Name is checked. But, when I forward engineer the name is not changed.

    BTW I just noticed that if I enable "Name Translation" then it seems to work. This is not at all intuitive or obvious, nor does it seem to be explained in the documentation.
    According to the help:
    Apply Name Translation: Controls whether formal names are translated to abbreviated names when the logical model is forward engineered to a relational model, and whether abbreviated names are translated to format names when a relational model is reverse engineered to the logical model. Name translation is applied only for valid names. In addition, translations between the words entity/attribute/key and table/column/index are performed.

  • Engineering logical subtypes to Relational model

    I have a logical model with subtype (box in box). When I forward engineer to a relational model there is nothing in the model to represent the subtypes. I was expecting (as in old Designer) to see a differentiator "type" column to be generated with a column check constraint based on my subtypes. In the logical model I selected "single table" as the implementation strategy.
    Note I also have these entities tagged as Dimensions and did notice the engineering dialog showed the substypes as hierarchies too.
    Am I missing a a preference setting somewhere?

    Hi Kent,
    I was expecting (as in old Designer) to see a differentiator "type" column to be generated support for that will be added later.
    Note I also have these entities tagged as Dimensionswhat do you expect - if you change implementation from "single table" to something else you'll get tables also classified as dimension, no other magic will be involved
    and did notice the engineering dialog showed the substypes as hierarchies tooI don't see your point here.
    Philip

Maybe you are looking for