2011-01-13
3,872 reads
2011-01-13
3,872 reads
2011-01-28 (first published: 2011-01-11)
1,794 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,923 reads
2011-01-06
2,826 reads
2011-01-04
3,425 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,474 reads
2010-12-30
2,952 reads
Understanding the basics of how T-SQL logic works in branching is important to ensure you code works as expected. This article will help you learn how this impacts control of flow language.
2013-06-21 (first published: 2010-12-30)
33,583 reads
By Vinay Thakur
Continuing from Day 5 where we covered notebooks, HuggingFace and fine tuning AI now...
By Steve Jones
This is kind of a funny page to look at. The next page has...
A while ago I blogged about a use case where a pipeline fails during...
I have a table I didn't design that has tons of repeating groups in...
Comments posted to this topic are about the item Writing as an Art and...
Comments posted to this topic are about the item String Similarity II
What is the range for the result from the EDIT_DISTANCE_SIMILARITY() function in SQL Server 2025?
See possible answers