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

Deploying an Updated Model with SQL Compare 16

By

In a previous post, I deployed a model to a database using SQL Compare...

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022

By

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...

Looking Back at the Redgate 2026 Company Kickoff

By

Last week I spent a few days in Cambridge, UK for the Redgate Company...

Read the latest Blogs

Forums

Adding and Dropping Columns II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Adding and Dropping Columns II

Leveraging DuckDB for OLAP Workloads: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Leveraging DuckDB for OLAP Workloads:...

More Documentation is Needed

By Steve Jones - SSC Editor

Comments posted to this topic are about the item More Documentation is Needed

Visit the forum

Question of the Day

Adding and Dropping Columns II

I have this table in my SQL Server 2022 database: 

CREATE TABLE [dbo].[CityList]
(
[CityNameID] [int] NOT NULL IDENTITY(1, 1),
[CityName] [varchar] (30) ,
[Country2] [char] (3),
[stateprovince2] [char] (2),
[Country] [char] (3),
[stateprovince] [char]
) ON [PRIMARY]
GO
I decide to drop the stateprovince2 and country2 columns. What code should I use?

See possible answers