Referential Integrity

Using SET NULL and SET DEFAULT with Foreign Key Constraints

  • Article

Cascading Updates and Deletes, introduced with SQL Server 2000, were such an important, crucial feature that it is hard to imagine providing referential integrity without them. One of the new features in SQL Server 2005 that hasn't gotten a lot of press from what I've read is the new options for the ON DELETE and ON UPDATE clauses: SET NULL and SET DEFAULT. Let's take a look!

2008-08-28

2,984 reads

Blogs

VMworld 2020 SQL Server session preview

By

Join me, David Klee, Microsoft Data Platform MVP and VMware vExpert, for a preview...

A new malware attack on SQL Server

By

Tencent Security has released a report (written in Chinese) describing a new malware attack by...

Azure Synapse Analytics overlooked features

By

There are some options in Azure Synapse Analytics that are not obvious that I...

Read the latest Blogs

Forums

Validate field in STaging before loading

By Bruin

I have a STaging table where I have defined all fields as Varchar(255), now...

Azure Log Analytics or SQL Profiler for AAS?

By imani_technology

I think you can use both SQL Server Profiler or Azure Log Analytics for...

Key Lookup to Clustered Index

By Adam Bean

Hey all, Been a bit since I've been down this road. Clearly I'd assume...

Visit the forum

Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers