T-SQL

External Article

Using DELETE CASCADE Option for Foreign Keys

  • Article

Referential integrity is a very important thing to consider when designing a database. In my years as a DBA I've seen database designs that sit on both ends of the spectrum, none at all and cases where every table is linked to multiple tables. While the later certainly can be a little more difficult to work with it ensures the integrity of your data stays intact. The other end provides much more flexibility when it comes to updating and deleting data from your database, whether it's being done through the application or directly on the backend, but has the issue of possible orphan records if things are not done properly. This tip will look at the DELETE CASCADE option when creating foreign key constraints and how it helps keep the referential integrity of your database intact.

2012-08-13

3,973 reads

Blogs

Setting FK Constraints in Data Modeler

By

One of the things a customer asked recently about Redgate Data Modeler was how...

Webinar: Navigating the Database Landscape in 2026

By

For a number of years, we’ve produced the State of the Database Landscape report,...

Claude AI Convinced Me Not to Build an iPad App

By

I coach volleyball and I do a lot of stat stuff on paper. I...

Read the latest Blogs

Forums

SSMS 22 Latest Update Crashing

By Phil Parkin

Hi all, I've just had to roll back my SSMS 22 version from 22.3.0,...

Transactional Replication setup issue

By DrAzure

Hi! I've been banging my head against the wall for 2 days now trying...

The Power of Data and Privacy

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Power of Data and...

Visit the forum

Question of the Day

What's the Date?

In SQL Server 2025, there is a new function that returns the current date without the time. What is it?

See possible answers