2012-11-30
2,442 reads
2012-11-30
2,442 reads
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
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
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,129 reads
By Brian Kelley
The concern that a particular technology is going to destroy the world seems to...
The STIG is detailed, which is a good thing, but I found myself wanting...
By Steve Jones
After my session at VSLive last week, I had a few questions from the...
Comments posted to this topic are about the item RegEx Functions III
Comments posted to this topic are about the item Optimized Locking in SQL Server...
Comments posted to this topic are about the item Finely Tuned Models
If I run the REGEXP_LIKE() function, does it match values in a case-sensitive fashion, or a case-insensitive fashion by default.
See possible answers