6 responses

  1. Kent Graziano
    June 12, 2013

    Another option to learn the repository model is to look at the PDFs in \datamodeler\reports\Reporting Schema diagrams.

    Using the reporting schema is one of the tips in my KScope13 talk. Sharing the models via the report tool in the modler is however a new trick.

    I have used the reports in SQL Developer, copied and modified them, and even just wrote some in SQL.

    I have one report that reproduces the old Designer report that turns relationships in the Logical model into the old Barker-style relationship sentences.

  2. tomasz
    June 13, 2013

    How do you create gnaw pictures ?

    • thatjeffsmith
      June 13, 2013

      What is a gnaw picture?

      95% of the pictures, including the animated GIFs on here, are created with Techsmith’s SnagIt or Camtasia.

  3. Mouhamed Elmasry
    June 13, 2013

    Hi, We are using sql developer data modeler 3.3, In my design, I have entities , a DFD, flows and processes, when I export to a reporting schema, I can see the entities in the DMRS_ENTITIES in the reporting schema, but not the processes and flows.

    Anyone have an idea why and how we can fix this?

    Thanks in advance.

    • thatjeffsmith
      June 13, 2013


  4. Thomas Rahn
    September 11, 2013

    Hi Jeff,

    Any chance of working around your concluding statement?
    “Meaning, I can’t use DML to update my models. That still happens via SQL Developer Data Modeler.”
    I have two specific use cases where I would like to update the model data in the reporting repository and then import the changes into the model in SQL Developer Data Modeler.

    1. I have two test versions of a database with several hundred tables. The data models of the databases are not identical. In one model I have added the table classification types of all the tables. I would now like to transfer the classification types to the second model for all tables that occur in both models. I can do this via sql in the repository, but I have not found a way to import the repository changes into the model. We have a dozen more such databases, so the time savings are substantial.

    2. Being able to colour in tables according to classification type makes large models much easier to understand. I would also like to colour tables according to responsible party (we have an even larger database with many responsible parties). If I could (mis)use the classification columns in the repository to store responsible party and then import the changes that would be real value added. As a workaround I envisage a procedure that copies the classification types from dmrs_tables to another table and then updates the classification type columns with the reponsible party information and then switches the data back when I want to see classification types.

    For future versions this would be high on my list of desired features and I am hoping there might even be a workaround to let me do it now. What do you say?


Leave a Reply




Back to top
mobile desktop