2011-01-21
3,885 reads
T-SQL
2011-01-13
3,872 reads
2011-01-28 (first published: 2011-01-11)
1,799 reads
Contiguous Time Periods
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
Identity Property Range Checking in SQL Server
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
Blogs
Advice I Like: Respect
By Steve Jones
“Don’t aim to have others like you; aim to have them respect you.” –...
Setting Up a Mac for Data Engineering and AI Work
If you work with data pipelines, SQL, notebooks, or machine learning models, a Mac...
Want to look at cloud reporting but not sure what the costs will be?
By ChrisJenkins
Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...
Forums
SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
locking down agent for new user on our dev machine
hi , a new user wants to be able to add sql agent jobs...
SQL Server Enum Implementation: A Single-Row View Strategy for Avoiding Magic Values
Comments posted to this topic are about the item SQL Server Enum Implementation: A...
Question of the Day
BIT_COUNT I
In SQL Server 2025, I have a table (dbo.UserPermission) that contains this data:
UserID UserPermissions 15 23 37What is returned when I run this code:
select bit_count(UserPermissions) as PermissionCount from dbo.UserPermission where UserID = 3;See possible answers