It’s worth a few moments to get your bearings when using a new program. Or maybe you’ve been using SQL Developer Data Modeler for awhile now, and just haven’t taken the time to understand how designs, models, and diagrams are handled.
This short post will fill in a few gaps and increase your comfort level with the tool, so please bear with me!
Organization and Navigation
Navigation is handled by the Browser. The Browser displays your designs, models, and diagrams in a ‘tree.’
When you open a design, it will prompt you to select one of more relational models. Those models will be opened, added to the tree, and the diagrams will be displayed.
SQL Developer Data Modeler’s Logical Model
Every relational model has a logical model, even if that logical model is null or empty. Wait, let me clarify that point further. Every design has a single logical model. So if you have 2 or more relational models, they ‘share’ a single logical model.
The diagrams are opened by default. If you want less clutter in your desktop, you can ‘hide’ the logical model and save the design. When you open the design again, the logical model diagram will not be shown. Another reason to ‘hide’ your logical models is the size of its diagram. If it has many entities, it can take a long time draw this on opening the design. ‘Hide’ it, and only open it on demand.
Your relational model can have zero, one, or many physical models. Physical models do not have diagrams.
It occurs to me, maybe a diagram will help describe how designs are organized?
This diagram uses the Barker Notation (although we also support Bachman and Information Engineering notations.) Thanks to @KentGraziano for the help getting this right. If you don’t have your own Oracle ACE Director available, try EntityModelingOrg for a quick primer on one-to-one, one-to-many, etc. relationships and how they’re represented in diagram form.
Opening, Saving, Showing Designs
As you open a design, it’s added to the tree. You can see in my first screenshot that I have 5 designs open. If I want to save a change to a design, the easiest way is to right-click on the design in the tree and select ‘Save Design.’ Otherwise, if you use the File > Save dialog, SQL Developer Data Modeler will prompt you for a design.
You can hide or show diagrams by right-clicking on the model. Hiding it doesn’t ‘close’ it – it just saves you space in your desktop.
Another fun fact: some of the application preferences are tied to specific designs. For example, if I create a new ‘Site’, it will prompt me for a design first. That’s right, you can have sites, domains, and other ‘preference’ or ‘setting’ level items tied to a particular design.
What’s a site? Read this to learn more about managing different physical implementations of your relational models.
In the case of sites, you can create a ‘global’ sites listing which is stored in an external file – a file that is external to the design.
Sharing Your Designs
The design is defined by a single xml file having a .dmd file extension. This file contains the listing of the many xml files used in the design. So when you want to email your design to someone else, you need the dmd file AND the directory containing all the XML files.
What About Datatype, Process, and Multidimensional Models?
I think that’s enough content for one post! We’ll pick this subject up at a future date