00:01
So to determine appropriate primary people is stable in the given relation data, we need to consider the unique national identity occasion required for each table.
00:14
So part two, we have to make sure that the most straightforward choice for the priority is the employee.
00:35
So the first step is to identify the unique person's name.
00:52
This assumes that each employee has a unique name within the data.
00:57
However, it is important to note that these assumptions may not hold in practice as people with the same name can exist.
01:03
Therefore, it means just the person's name as the primary, it might not be the best.
01:09
A better approach could be a unique identifier for each employee such as an employee id for each employee.
01:21
If such id exists, it should be considered as a primary key.
01:25
If not, you might need to create one or use a combination of attributes.
01:29
For example, person's id and email.
01:41
To ensure uniqueness, the campaign must be employment -related...