2012-11-30
2,415 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
Presenting with Visual Studio Code
A while back I wrote a quick post on setting up key mappings in...
Advice I Like: In 100 Years
By Steve Jones
In 100 years a lot of what we take to be true now will...
Forums
is it true we cant debug c# scripts in ssis anymore under vs
Hi, i'm running vs2022. I'm trying out a c# script that i'd like to...
Missing the Jaro Winkler Distance
Comments posted to this topic are about the item Missing the Jaro Winkler Distance
Question of the Day
Missing the Jaro Winkler Distance
I upgraded a SQL Server 2019 instance to SQL Server 2025. I wanted to test the fuzzy string search functions. I run this code:
SELECT JARO_WINKLER_DISTANCE('tim', 'tom')
I get this error message:Msg 195, Level 15, State 10, Line 1 'JARO_WINKLER_DISTANCE' is not a recognized built-in function name.What is wrong? See possible answers