Additional Articles


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.

You rated this post out of 5. Change rating

2022-10-05

Blogs

When Your Microsoft Fabric Capacity Runs Out: Optimize, Scale Up, Scale Out, or Isolate?

By

Microsoft Fabric makes it wonderfully easy to put many analytics workloads on one platform....

Accessing the Data API Builder MCP Server from VS Code

By

I recently started playing with the MCP Server for SQL Server, which is a...

From DBA or Data Engineer to AI Engineer: A Realistic Path

By

If you spend your days tuning queries, managing pipelines, or keeping a production database...

Read the latest Blogs

Forums

BIT_COUNT() V

By Steve Jones - SSC Editor

Comments posted to this topic are about the item BIT_COUNT() V

How We Reduced SQL Server Infrastructure Costs by 33% on AWS: Lessons From a Database Operations Manager

By Pravalik Medi

Comments posted to this topic are about the item How We Reduced SQL Server...

An Eventual Consistency Scam

By Steve Jones - SSC Editor

Comments posted to this topic are about the item An Eventual Consistency Scam

Visit the forum

Question of the Day

BIT_COUNT() V

What does this return on SQL Server 2025?

select bit_count(null)

See possible answers