What is a database design?
The design
database, as the name can suggest, is like the design of the house, although this term can also be used to refer to the actual database design. The design process is something like a plan that outlines the details of the database, from the relationships between tables to what information is important and how the data will be implemented. In addition to helping the builder know what tables and information to collect, design uses name conventions and spelling errors are checked before completing the database. The database also undergoes normalization that seeks to remove redundancy during the design process. Without the first design of the design, the database creator can easily spoil the order of tables or the primary key for tables or simply omit several sections, among many other potential errors.
The first step of the database design is to know the purpose of the database. There are no diagrams or abstract representations; The designer is just thinking about databases objects. Some information may be enrolled but a designerIn general, he considers the best way to organize and use a database.
The designer also creates four data models. The conceptual model is a simple diagram that shows table names. Then a logical data model is created and fills in the tables with the primary key and the information to be collected. The primary key is the name of the column, which makes it unique and tells users the purpose of the column. Relationships between tables are also described in detail during this database design phase.
In the Entity-Relationship model, the designer focuses more on relationships and less primary keys. This model can sometimes be skipped, but helps to show how entities interact with each other. In the physical data model, live information is supplied to the database design.
during each phase of the model magic of tables and primary keys must be checked. The naming of conventions is also used, so useThe studies know how to enter data. For example, the table could be named "Thistable", "This_table", "This table" or "this.to.to", based on the name of the naming Convention selected by the database designer. Spelling must be checked because the error can cause relationship problems when the database is created.
Normalization rules are also used on a database model. These rules eliminate repeating data, dissolve large tables into small tables, and ensure that relations are optimized. Normalization of the database design is the last step and will help the designers to determine whether the database is functional or whether it is necessary to go or rework.