2012-11-30
2,414 reads
Referential Integrity
Using SET NULL and SET DEFAULT with Foreign Key Constraints
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
Avoid Untrusted Constraints in SQL Server
Some time ago, I loaded a large set of data into one my tables. To speed up the load, I disabled the FOREIGN KEY and CHECK constraints on the table and then re-enabled them after the load was complete. I am now finding that some of the loaded data was referentially invalid. What happened?
2008-07-18
3,000 reads
Change column type on constrained columns
Use this proc if you need to alter a column that is part of a primery key
2008-02-04 (first published: 2007-12-10)
1,120 reads
Blogs
Using CAT for Testing of Data Agents
In last months one of the scenarios where you can use AI has been...
Are you getting value from your reporting?
By ChrisJenkins
Do you spend so long manipulating your data into something vaguely useful that you...
The Book of Redgate: SQL Server Central
By Steve Jones
It was neat to stumble on this in the book, a piece by me,...
Forums
Which 'Where' statement conditional upon a variable
Thanks in advance for any clues on this. I am trying to write a...
Backup to Immutable Storage
Comments posted to this topic are about the item Backup to Immutable Storage
Microsoft Security Changes and SQL Server
Comments posted to this topic are about the item Microsoft Security Changes and SQL...
Question of the Day
Backup to Immutable Storage
In SQL Server 2025, a backup can be made on Azure Immutable Storage. What changes in how the backup is created?
See possible answers