In an ERD, when you represent the columns that exist in entities, you might only want to show their names but not any other property like their types since datatype is usually not required in early communication of data structure but is only required when implementing a database. In order to simplify an ERD and to avoid giving wrong information, you can hide the datatype, so that only the column names are left. For your convenience, Visual Paradigm supports hiding the datatype of columns, please follow the simple steps below. Read more
Last week, we showed you how to assign entities in an ERD to a schema. One of our users ask if there is any way to group entities in a logical manner, rather than setting the schema property reserved for physical database.
The answer is yes. You can make use of model or UML package to store and categories the entities in logical groups. The grouping can be seen in both the Model Structure and diagram. In this article, we will show you how to group entities in ERD database designer. In order to perform the steps described in this article, make sure you have Visual Paradigm installed.
Entity-Relationship Diagrams (ERDs) come in 3 types in general. They describe data models on 3 levels of abstraction – conceptual, logical and physical, ranging from high-level ideas to details required for implementation. With Visual Paradigm, you can systematically and easily progress through these stages of development in data modeling.
Far from a copy & paste function only, you can actually develop a logical or physical design from a conceptual diagram, with the design tracing ability.
For example, if a new staff comes on board to work on a project’s physical design ERD, he/she can click on a database table to trace where this idea originally comes from in the conceptual diagram (to which it is inherently linked by Visual Paradigm). This function will not only bring relief to the staff but also help safeguard the project’s quality along the way.
In this article, we will show you an example on how to create a conceptual ERD and transit it to a physical ERD, from which you can generate a DLL file for database implementation. Read more
In helping you organize your modeling project, use cases can act as generic containers for all software development artifacts. Development teams can group and locate design artifacts by navigating use cases.
In this tutorial we are going to show you how to create a new data model (i.e. entity relationship diagram) and associate that with a use case. And in future, you can easily identify existing associations as such by use cases and conveniently, be taken to the related diagrams right on the spot in just a few clicks.
Visual Paradigm for UML (VP-UML) comes with an ERD database designer where database developers can model physical database with Entity Relationship Diagram. The database designer supports popular database constructs like database table (called Entity in VP-UML), View, Sequence, Stored Procedure, Trigger, etc, supporting the need of database modeling for any kind of database management systems.