Key Differences between Primary Key vs Foreign Key
- A primary key constraint is a column that uniquely identifies every row in the table of the relational database management system, while a foreign key is a column that creates a relationship between two tables.
- The primary Key never accepts null values, whereas the foreign key may accept multiple null values.
- You can have only a single primary key in a table, while you can have multiple foreign keys in a table.
- The value of the primary key can’t be removed from the parent table, whereas the value of foreign key value can be removed from the child table.
- No two rows can have any identical values for a primary key; on the other hand, a foreign key can contain duplicate values.
- There is no limitation in inserting the values into the table column while inserting any value in the foreign key table; ensure that the value is present into a column of a primary key.
What are Keys?
Keys are attribute that helps you to identify a row(tuple) in a relation(table). They allow you to find the relationship between two tables. Keys help you uniquely identify a row in a table by a combination of one or more columns in that table. The database key is also helpful for finding a unique record or row from the table.
What is Primary Key?
A primary key constrain is a column or group of columns that uniquely identifies every row in the table of the relational database management system. It cannot be a duplicate, meaning the same value should not appear more than once in the table.
A table can not have more than one primary key. Primary key can be defined at the column or the table level. If you create a composite primary key, it should be defined at the table level.
What is Foreign Key?
Foreign key is a column that creates a relationship between two tables. The purpose of the Foreign key is to maintain data integrity and allow navigation between two different instances of an entity. It acts as a cross-reference between two tables as it references the primary key of another table. Every relationship in the database should be supported by a foreign key.
Difference between Primary Key and Foreign Key
Here is the important difference between Primary key and Foreign key:
|Primary Key||Foreign Key|
|A primary key constrain is a column or group of columns that uniquely identifies every row in the table of the relational database management system.||Foreign key is a column that creates a relationship between two tables.|
|It helps you to uniquely identify a record in the table.||It is a field in the table that is a primary key of another table.|
|Primary Key never accepts null values.||A foreign key may accept multiple null values.|
|The primary key is a clustered index, and data in the DBMS table are physically organized in the sequence of the clustered index.||A foreign key cannot automatically create an index, clustered, or non-clustered.|
|You can have the single Primary key in a table.||You can have multiple foreign keys in a table.|
|The value of the primary key can’t be removed from the parent table.||The value of foreign key value can be removed from the child table.|
|You can define the primary key implicitly on the temporary tables.||You cannot define foreign keys on the local or global temporary tables.|
|Primary key is a clustered index.||By default, it is not a clustered index.|
|No two rows can have any identical values for a primary key.||A foreign key can contain duplicate values.|
|There is no limitation in inserting the values into the table column.||While inserting any value in the foreign key table, ensure that the value is present into a column of a primary key.|
What is Database Relationship?
The database relationship is associations between one or more tables that are created using join statements. It is used to efficiently retrieve data from the database. There are primarily three types of relationships 1) One-to-One, 2) One-to-many, 3) Many-to-many.
Why use Primary Key?
Here are the cons/benefits of using primary key:
- The main aim of the primary key is to identify each and every record in the database table.
- You can use a primary key when you do not allow someone to enter null values.
- If you delete or update records, the action you specified will be undertaken to make sure data integrity.
- Perform restrict operation to rejects delete or update operation for the parent table.
- Data are organized in a sequence of clustered index whenever you physically organize DBMS table.
Why use Foreign Key?
Here are the important reasons of using foreign key:
- Foreign keys help you to migrate entities using a primary key from the parent table.
- A foreign key enables you to link two or more tables together.
- It makes your database data consistent.
- A foreign key can be used to match a column or combination of columns with primary key in a parent table.
- SQL foreign key constraint is used to make sure the referential integrity of the data parent to match values in the child table.
Example of Primary Key
Below is the syntax of Primary Key:
CREATE TABLE <Table-Name> ( Column1 datatype, Column2 datatype, PRIMARY KEY (Column-Name) . );
- Table_Name is the name of the table you have to create.
- Column_Name is the name of the column having the primary key.
|StudID||Roll No||First Name||Last Name|
In the above example, we have created a student table with columns like StudID, Roll No, First Name, Last Name, and Email. StudID is chosen as a primary key because it can uniquely identify other rows in the table.
Example of Foreign Key
Below is the syntax of Foreign Key:
CREATE TABLE <Table Name>( column1 datatype, column2 datatype, constraint (name of constraint) FOREIGN KEY [column1, column2...] REFERENCES [primary key table name] (List of primary key table column) ...);
- The parameter Table Name indicates the name of the table that you are going to create.
- The parameters column1, column2… depicts the columns that need to be added to the table.
- Constraint denotes the name of constraint you are creating.
- References indicate a table with the primary key.
In the above example, we have two tables, a teacher and a department in a school. However, there is no way to see which search works in which department.
In this table, adding the foreign key in Deptcode to the Teacher name, we can create a relationship between the two tables.
This concept is also known as Referential Integrity.