Cascading referential integrity constraint

Cascading referential integrity constraint allow to define the action MS sql server should taken when a user attempt to delete or update a key to which exiting foreign key points.

For Example:- If you delete row with I'd =1 from blender table , show row with I'd =3 from tblperson table become an orphan record. You won't be able tell the gender for this row, therefore, Cascading referential integrity constraint can be used to define actions MS SQL Server should take when this happens. By default, we get an error and the DELETE or UPDATE statement is reverted.