Er diagram in oracle sql developer software#

And to make sure that their idea of an ERD matches up to mine, regardless of who is ‘right’ or not. When I do an import of a data dictionary (which is a live, breathing instance of Oracle in this case), SQL Developer Data Modeler builds for me by default a Relational Model which is also composed of one or more Physical models.Īnd that’s USUALLY enough for what people are looking for.īut when someone says they NEED an ERD, I should know better to clarify what their requirements actually are. I have a nasty habit of calling THIS an ERD This is NOT an ERD

So the Logical or Entity based diagram is completely separate from the Physical diagram. In a logical model, I might call an ‘entity’ a ‘customer.’ When I go to build the system physically in a databse like Oracle, that might actually be composed of one or more TABLEs. An Entity is a 1000 ft view of how you are going to handle a uniquely identifiable piece of data – kind of like how an atom used be seen as the smallest physical piece of matter. It stands for ‘Entity.’ Entities are a much more abstract concept than a table. Which in this case is generally a diagram of their tables and views and the relationships between them. – they are asking for a diagram which displays and describes the PHYSICAL properties of their data model for their application.

When talking to customers, ninety-percent of the time, when they say –

Er diagram in oracle sql developer software#

So I’ve been working with data modeling software for almost 15 years and on a regular basis for the last 8 or 9 years. And then when someone calls me out, my first reaction is to defend my ‘shortcut’ thinking instead of re-evaluating my set of assumptions. I take something for granted or assume something for so long, that it corrupts my original learning or understanding of a concept.