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

On Speaking Well

By

Professor Patrick Winston of MIT used to give a one-hour talk about how to...

Monday Monitor Tips: Oracle Custom Metrics

By

One of the popular features of Redgate Monitor has been the ability to add...

Walking Through a Planned Failover: SQL Server Always On Availability Groups on Kubernetes

By

When building the sql-on-k8s-operator, I wanted to make sure it could handle both planned...

Read the latest Blogs

Forums

Analysis of Locking Issues on Secondary Replicas in AlwaysOn Availability Groups

By abdalah.mehdoini

We have an AlwaysOn architecture with four replicas: two running in synchronous commit mode...

The Vector Data Type

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Vector Data Type

What Power BI DirectQuery does to your SQL Server (and how to fix it)

By kat.korson@redeagle.tech

Comments posted to this topic are about the item What Power BI DirectQuery does...

Visit the forum

Question of the Day

The Vector Data Type

What is the vector data type in SQL Server?

See possible answers