This approach has many conflicts with characteristics of relation table, i. E. “Each row/column intersection represents a single data value” This approach would result to use lot of complex queries which could lead to performance degrade as it onuses lot of time when used for reporting purposes, having seen the above problems It is considered as a bad design while designing a relational database management system.
2.Create several new attributes, one for each value of the multivolume attribute as shown in table below. Employee Table MME_no Degreed Degreed Degreed Banger Reedy Aura B.
TECH MS MSP MOBS LB By looking at the above design there is a possibility of two problems, firstly the existence of blank spaces in the table that are the NULL values, while designing the database it is recommended to eliminate unnecessary null aloes which are existing in the above table.Second problem is the above table has only three fields to accommodate the degrees as per our business rule, here we cannot accommodate an employee who holds more than three degrees. So this is also considered as a bad design of relational database system. 3. The given business rule clearly states that employee and degree have one- to-many (1 :M) relationships.
From this business rule we are going to create a new entity that will contain each attribute value as a record. Using primary key and foreign key pair.