2011-01-21
3,885 reads
2011-01-21
3,885 reads
2011-01-13
3,872 reads
2011-01-28 (first published: 2011-01-11)
1,796 reads
It is always more efficient to maintain referential integrity by using constraints rather than triggers. Sometimes it isn't obvious how to do this. Until a recent idea by Alex Kuznetsov, the history table presented problems for checking data that were difficult to solve with constraints. Joe Celko explains.
2011-01-11
3,294 reads
2011-01-10
2,924 reads
2011-01-06
2,826 reads
2011-01-04
3,427 reads
This article examines practical methods of managing and monitoring large tables which make use of the IDENTITY property.
2011-01-04
3,913 reads
2011-01-03
3,475 reads
2010-12-30
2,953 reads
By DataOnWheels
Two years ago, two things happened within a few days of each other. I...
By gbargsley
This is it. The final chapter of PowerShell Strikes Back. Over the past four...
By Arun Sirpal
Claude is more than a chat window. The desktop experience includes structured workspaces, generated...
Good Morning. I have a T-SQL Script which has been developed to execute a...
Comments posted to this topic are about the item Stop Prompting Your AI Agent....
Comments posted to this topic are about the item Finish the quote
Finish this quote (for a fun Memorial Day question):
Do not try and bend the spoon. That's impossible. ...See possible answers