database design

Database design scenario Currently, the school uses a non-computerized database system to store the following information about students. List of subjects and courses registered by students. The system occupies a lot of space and there are many duplicate items, but some of them are erroneous and search time is very long.

Conceptual design of databases is a difficult task for novice database designers (students, etc.), so it is particularly challenging for database educators. In the design of database design, two general ways of top-down and bottom-up are often emphasized. In this paper, we examine the performance of students in these two methods empirically in a conceptual data modeling exercise. Our results show that previous database education has had a profound effect on it

In most application development projects, the technology used to persist data is a relational database. Database designers are responsible for defining detailed database designs, including tables, indexes, views, constraints, triggers, stored procedures, and other database-specific structures necessary for storing, retrieving, and deleting persistent objects. This information is managed in the deliverables: data model.

Database design is the process of generating a detailed data model of the database. This data model contains all the necessary logical and physical design choices and physical storage parameters necessary to generate the design in the data definition language and can be used to create a database . The full attribute data model contains detailed properties for each entity. The term database design can be used to describe various parts of the overall database system design. In principle, and most accurately, it can be thought of as the logical design of the underlying data structure used to store the data. In the relational model, these are tables and views. In the object database, entities and relationships are mapped directly to object classes and naming relationships.

Fragmentation is a very old concept in centralized database design. Database partitioning is the horizontal partitioning of the data in the database. Individual partitions are called slices or database slices. Each piece is stored in a separate database server instance to distribute the load. This means that the database is divided into separate databases that do not share public data. Since you can add fragments for unlimited extensions, it allows for horizontal expansion of any database system. Today, most databases such as MongoDB and MySQL support fragmentation. Therefore, technology is mature enough to become mainstream. Block chains have existed for a long time, but mainstream sharding adjustment is still not visible. One of the recommended ways is to use multiple fragments. Each piece can be processed according to the address range of the sender.