Technical Article

Transaction locking and row versioning guide

In any database, mismanagement of transactions often leads to contention and performance problems in systems that have many users. As the number of users that access the data increases, it becomes important to have applications that use transactions efficiently. This guide describes the locking and row versioning mechanisms the SQL Server Database Engine uses to ensure the physical integrity of each transaction and provides information on how applications can control transactions efficiently.

Blogs

Setting Up a Mac for Data Engineering and AI Work

By

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

Have you been thinking about migrating your reporting to Microsoft Fabric or Snowflake but...

The Joyful Craftsmen and the Revolt BI join forces

By

The Joyful Craftsmen has become the new owner of Revolt BI. The merger creates...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

SQL Server Enum Implementation: A Single-Row View Strategy for Avoiding Magic Values

By Ivica Borscak

Comments posted to this topic are about the item SQL Server Enum Implementation: A...

BIT_COUNT I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item BIT_COUNT I

Visit the forum

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
37
What is returned when I run this code: 
select bit_count(UserPermissions) as PermissionCount
from dbo.UserPermission
where UserID = 3;

See possible answers