SQL - Candidate Key
In SQL Server, a candidate key is a set of one or more columns that can uniquely identify a row in a table. It is a candidate for being chosen as the primary key of the table. A candidate key must satisfy two properties:
- Uniqueness: Each value in the candidate key must be unique within the table. No two rows can have the same combination of values in the candidate key columns.
- Minimality: No proper subset of the candidate key should have the uniqueness property. In other words, removing any column from the candidate key would result in losing the uniqueness property.
Candidate keys provide a means to identify and distinguish rows in a table uniquely. They play a crucial role in database design when determining the primary key of a table.
Let's consider an example of table named "Students" with the following columns:
-
StudentID (Primary Key)
- SocialSecurityNumber (Candidate Key)
- StudentEmail (Candidate Key)
- StudentName
- Birthdate
In this example, the table "Students" represents student records in a school database.
-
StudentID: This is chosen as the Primary Key. It uniquely identifies each student in the table.
-
SocialSecurityNumber: This is also a unique attribute that could identify each student. It's a candidate key because it can be used to uniquely identify students, but since "StudentID" is already chosen as the Primary Key, "SocialSecurityNumber" becomes an Alternate Key.
-
StudentEmail: Similarly, "StudentEmail" is another unique attribute that could identify each student. It's also a candidate key. However, since "StudentID" is already the Primary Key, "StudentEmail" becomes another Alternate Key.
Let's insert some sample data into the "Students" table:
Table: Students
StudentID |
SocialSecurityNumber |
StudentEmail |
StudentName |
Birthdate |
1 |
123-45-6789 |
john@example.com |
John |
2000-05-15 |
2 |
987-65-4321 |
sarah@example.com |
Sarah |
2001-08-20 |
3 |
555-55-5555 |
michael@example.com |
Michael |
1999-02-10 |
In this example, "StudentID" is the Primary Key, and it uniquely identifies each student. "SocialSecurityNumber" and "StudentEmail" are both candidate keys, but they are not chosen as the Primary Key. Instead, they serve as alternate means of uniquely identifying students.
Having candidate keys allows you to perform various operations in the database, such as searching for students using different attributes or ensuring data integrity by preventing duplicate values in these unique columns.