SQL Server BasicsWhat is SQL Server database?What is RDBMS?What is Normalization?Why we use Denormalization?What_is_SQL?What is PL/SQL?Difference between SQL and PL/SQLDatabase TableOne to One RelationshipOne to Many RelationshipMany to Many RelationshipMany to One RelationshipString Data TypesNumber Data TypesDate Data TypesOther Data TypesCreate DatabaseDrop DatabaseCreating and Managing Users in SQL ServerCreate TableAlter TableDrop TableConstraints in SQL serverPrimary KeyForeign KeyUnique KeyCandidate KeyComposite KeyDifference between primary key and candidate keyPrimary key and foreign key relationshipSurrogate KeyCascading Referential Integrity ConstraintsSelf Referential Integrity ConstraintsInsert into statementInsert multiple recordsUpdate statementDelete statementTruncate statementDifference between Delete and TruncateAlias in SQL ServerSelect statementSelect DistinctSelect TopSelect IntoNull Functions(ISNULL(),NULLIF(),COALESCE())Sub QueryIdentity ColumnSequence objectDifference between sequence and identity columnSQL Server ClausesWHERE ClauseOrder By ClauseTop N ClauseGroup By ClauseHaving ClauseDifference between Where and HavingSQL Server OperatorsArithmetic OperatorsComparison OperatorsLogical OperatorsBitwise OperatorsAny OperatorsAll OperatorsUnion OperatorsUnion All OperatorsDifference between Union and Union AllIntersect OperatorExcept OperatorDifference between Except and IntersectJoinsInner JoinLeft JoinRight JoinFull JoinSelf JoinCross JoinViewsWhat are views?Create views using SSMSIndexed ViewsComplex ViewsCheck Option in ViewCheck Encryption in ViewSchema Binding Option in ViewRead-only ViewsUpdatable ViewsAdvantages and disadvantages of viewsCreate multiple views on one tableCan we implement index on views?Can we Perform Insert, update, delete operation on views?Stored Procedure and FunctionsWhat are Stored Procedures?Why we use stored procedures?Passing parameters to Stored procedureUser-Defined FunctionsDifference between UDF and Stored procedurePre-Defined Functions@@Indentity and Scope_IndentityNULLIF, ISNULL and COALESCE
Previous
Next

What are Cascading Referential Integrity Constraints in SQL Server?

Cascading referential integrity constraints in SQL Server are used to maintain data consistency and integrity between related tables. They define the actions that should be taken when a referenced record is modified (updated or deleted). These actions can be automatically applied to ensure that the relationships between tables are maintained correctly.

In SQL Server, there are two types of cascading referential integrity actions that can be defined:

  1. Cascade Update: When a referenced record is updated, the changes are cascaded to the related records in the referencing table(s).
  2. Cascade Delete: When a referenced record is deleted, the deletion is cascaded to the related records in the referencing table(s).

To illustrate these concepts, let's consider an example with two tables: "Orders" and "OrderItems". The "Orders" table contains information about orders, and the "OrderItems" table contains details about individual items in each order. Each order item is associated with a specific order through a foreign key relationship.

Here are the table definitions:


CREATE TABLE Orders (
    OrderID INT PRIMARY KEY,
    OrderDate DATE
);

CREATE TABLE OrderItems (
    ItemID INT PRIMARY KEY,
    OrderID INT,
    ItemName VARCHAR(50),
    CONSTRAINT FK_OrderItems_Orders FOREIGN KEY (OrderID) REFERENCES Orders(OrderID)
        ON UPDATE CASCADE
        ON DELETE CASCADE
);

In this example, the "OrderItems" table has a foreign key constraint (FK_OrderItems_Orders) that references the "Orders" table. Both the ON UPDATE CASCADE and ON DELETE CASCADE clauses are specified, indicating that cascading actions should be performed on both update and delete operations.
If we insert some data into the tables: 


INSERT INTO Orders (OrderID, OrderDate) VALUES (1, '2023-05-01');
INSERT INTO Orders (OrderID, OrderDate) VALUES (2, '2023-05-02');

INSERT INTO OrderItems (ItemID, OrderID, ItemName) VALUES (1, 1, 'Item 1');
INSERT INTO OrderItems (ItemID, OrderID, ItemName) VALUES (2, 1, 'Item 2');
INSERT INTO OrderItems (ItemID, OrderID, ItemName) VALUES (3, 2, 'Item 3');

Now, if we update the OrderID in the "Orders" table, the changes will cascade to the "OrderItems" table due to the cascading referential integrity constraint:


UPDATE Orders SET OrderID = 3 WHERE OrderID = 1;

After executing this update statement, the OrderID in the "OrderItems" table will also be updated automatically to reflect the change.

Similarly, if we delete an order from the "Orders" table, the corresponding order items will be automatically deleted due to the cascading referential integrity constraint: 


DELETE FROM Orders WHERE OrderID = 2;

After executing this delete statement, the order with OrderID 2 and its associated order items will be deleted from both the "Orders" and "OrderItems" tables.

This example demonstrates how cascading referential integrity constraints can help maintain data consistency and automatically handle changes in related tables. It simplifies the management of data relationships and reduces the risk of orphaned or inconsistent data.

Previous
Next