My assignment requires that I have an ER diagram that shows the dependencies between the objects in my solution. Mine consists of several procedures, tables, a trigger and a sequence. Does anyone know if these objects are permitted in a SQL ER diagram? I ask this because the example shown by my lecturer consisted only of tables. If these objects are allowed in an ER diagram, what is the proper way to represent them?
My assignment requires that I have an ER diagram that shows the dependencies between
Share
No, an ER diagram should not contain procedures, triggers nor sequences.
An Entity-Relashioship Diagram is used to represent the relashionships between entities in a database. Procedures, triggers and sequences do not contribute to the relashionship representations.