Vertical Fragmentation: – Every single site might not need every columns or attributes of a relation or tables, which would specify the need for a dissimilar type of fragmentation. Vertical fragmentation divides a table or relation "vertically" by means of columns or attributes. A vertical fragment of an attributes or relation keeps only sure columns or attributes of the relation or tables. For an instance, an individual might want to fragment the EMPLOYEE relation or table into two (2) vertical fragments. The first fragment contains personal information like FName, MName, LName, DOB, Address and Gender and the second fragment contains work related information like ManagerID, Salary, EmpID, DeptID. This vertical fragmentation is not fairly correct for the reason that, if the two (2) fragments are kept distinctly, an individual cannot put the unique employee rows or tuples back together, as there is no common column or attribute between the two (2) fragments. It is essential to comprise the primary key or a number of candidate key columns or attribute in every single vertical fragment as a result that the full table or relation can be recreated from the fragments. Therefore, an individual should add the EmpID column or attribute to the personal information fragment.
It can be noted over here that every single horizontal fragment on a table or relation R can be quantified by means of