2012-11-30
2,454 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,135 reads
Blogs
Architecting Zero Downtime Deployments–Day of Data Boston
By Steve Jones
Here are the resources for my talk at Day of Data Boston. Slides –...
The Book of Redgate:A Prehistory
By Steve Jones
I’ve covered the values in a number of previous posts on the Book of...
Evidence-bound: what AgentDBA will and won’t link
By Arun Sirpal
When the evidence names the database, it says so. When it doesn’t, it stops....
Forums
Split Large Queries in Athena with a Simple Modulo Trick
Comments posted to this topic are about the item Split Large Queries in Athena...
Finding Trailing Spaces
Comments posted to this topic are about the item Finding Trailing Spaces
Question of the Day
Finding Trailing Spaces
I have some data in a SQL Server 2025 database. It looks like this for the dbo.Customer table:
CustomerID CustomerName PreferredName 1 Steve Steve 2 Andy Andy 3 Brian Brian 4 Allan Allan 5 Devin Devin 6 Steve Steve 7 Sally SallyI want to detect which names have a single trailing space. The CustomerName is a varchar() and the PreferredName is a CHAR(). Does this query detect the problem rows?
SELECT
CustomerID,
CustomerName,
PreferredName
FROM Customer
WHERE CustomerName <> RTRIM(CustomerName)
OR PreferredName <> RTRIM(PreferredName); See possible answers