What is Entity-Relationship Modeling?

Entity-relationship modeling is a logical design approach that follows to remove data redundancy. It is considered that a business takes orders and sells products to users.

In the initial days of evaluating, long before relational databases, when it can first transfer this information to a computer, it is possibly captured the original paper order as an individual fat data with several fields. Such data can easily have been 1000 bytes delivered across 50 fields. The line elements of the order were defined as a repeating set of fields embedded in the master data. It is receiving this data on the computer was very beneficial, but it can fastly learn some basic lessons about saving and manipulating data.

The user name and address appeared several times because this data was repeated whenever a new rule was taken. Inconsistencies in the data were uncontrolled because some instances of the user address were autonomous, and updating the user’s address was a dirty transaction.

The software systems used for fetching and operating the data became complex and disorganized because they needed careful consideration to the processing algorithms for connecting these groups of tables. It is required a database system that was very good at connecting tables. This concrete the way for the relational database revolution where the database was concerned to only this task.

Entity-relationship modeling is a discipline that can highlight the microscopic relationships between data elements. The largest design form of entity-relationship modeling is to eliminate all redundancy in the data. This is more useful to transaction processing because it creates transactions very simple and deterministic.

The transaction of updating a user address can devolve to an individual data lookup in a user address master table. This lookup is reserved by a user address key that represents the uniqueness of the user address data and enables an indexed lookup that is completely fast. It is secure to say that the achievement of transaction processing in relational databases is generally due to the development of entity-relationship modeling.

The entity-relationship model for the enterprise has thousands of logical entities. High-end enterprise resource planning (ERP) systems such as SAP have thousands of entities. Each entity generally turns into a physical table when the database is performed.

End users cannot learn or learn an entity-relationship model. End users cannot handle an entity-relationship model. There is no GUI (graphical user interface) that takes a general entity-relationship model and creates it accessible by end-users.

The software cannot generously query a general entity-relationship model. Cost-based optimizers that try to do this are notorious for creating the wrong choices, with disastrous results for performance. The need of the entity-relationship modeling technique defeats the aim of data warehousing, including intuitive and high-performance recovery of information.