Referential Integrity

External Article

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

What is KTLO? Keep The Lights On vs Project Work in Agile

By

🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...

The PASS Summit on Tour in Dallas

By

The PASS Summit goes on tour this year, with a September stop in Dallas....

SQL Server Auto-settings: The Good, the Bad, and the Ugly

By

Settings That Could Be Hurting Your Performance If you’ve ever created a new SQL...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

Formatting Dates and Times: The SQL Dialect Divide

By dbakevlar

Comments posted to this topic are about the item Formatting Dates and Times: The...

Query Plan Regressions --

By dbakevlar

Comments posted to this topic are about the item Query Plan Regressions --

Visit the forum

Question of the Day

Query Plan Regressions --

For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question:  You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?

See possible answers