The BIT data type is an awkward fit for a SQL database. It doesn't have just two values, and it can do unexpected things in expressions. What is worse, it is a flag rather than a predicate, and so its overuse, along with bit masks, is a prime candidate for being listed as a 'SQL Code Smell'. Joe Celko makes the case.
2011-01-24
3,676 reads
2011-01-21
3,885 reads
2011-01-13
3,872 reads
2011-01-28 (first published: 2011-01-11)
1,792 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,473 reads
By Steve Jones
For a number of years, we’ve produced the State of the Database Landscape report,...
By Steve Jones
I coach volleyball and I do a lot of stat stuff on paper. I...
By Steve Jones
dolorblindness – n. the frustration that you’ll never be able to understand another person’s...
Comments posted to this topic are about the item The Power of Data and...
Comments posted to this topic are about the item What's the Date?
Comments posted to this topic are about the item Two New Shortcuts for Fabric...
In SQL Server 2025, there is a new function that returns the current date without the time. What is it?
See possible answers