SQL Developer Data Modeler Repository

Question

Hi,
I would like to know how to save all my applications into the Data Modeler Repository instead of doing it piece by piece and having to create a dmd file for every single application I imported into Data Modeler.
In Oracle Designer, everything is in the repository and I can run reports against the tables and views belonging to that repository. So, I can produce a pdf documentation out of it. Can we do the same with Data Modeler?
Thank you!

Answer 1

Hello Anonymous,
I'll start with your first comment - "I would like to know how to save all my applications into the Data Modeler Repository ". The Repository is just for reporting purposes, as Dimitar points outs, so saving all your applications in the Data Modeler is merely File - Save. This action saves the current design (with all its models) to the file system. The main premise here is that the Data Modeler is a file based product and all models and designs are saved locally to the file system. This is a positive move for many customers who are now building applications in Java or using any of the application development environments that work with a variety of files. They are taking all the artifacts and placing them under version control using open source versing tools like Subversion. Using the Data Modeler, they can do the same.
For reporting you have a choice, one of which has also been explained. The action of creating a schema before you export the design is a one off step. Following on from this you can export new versions of the model to the same repository. The reason we did this was that many of the Designer audience wanted to write and run their own reports. So here you have a set of tables that you can write whatever SQL query you want to use.
The other reporting option is to use the integrated reports in the product and you do not have to export the design or open another product or write SQL.
Have you used the Design Rules in the Data Modeler? These are a set of "reports" for quality assurance purposes. There are many of these reports at all levels of the design which verify that your model is defined according to a set of database rules and general business rules and if you like, you can add your own rules.
I attended ODTUG last week in LA and was really pleased to listen to a number of talks by well seasoned Designer users who have successfully transitioned to the Data Modeler and who had many positive experiences.
Yes, the tools are different - but the one tool was not designed to replace the other - Data Modeler does none of the application design and generation that Designer does, those customers who have wanted to replace one tool (people are moving to the data Modeler from different tools) with the Data Modeler, have reported to me that they are pleased with the change.
Regards
Sue Harper
Product Manager