Part 1: How to solve the transactional issues of isolation levels
Transaction Isolation levels are described in terms of which concurrency side-effects, such as dirty reads or phantom reads, are allowed.
2013-05-01
10,148 reads
Isolation Levels
2012-11-21
2,105 reads
2012-04-19
2,013 reads
2010-07-06
3,085 reads
2009-03-19
3,985 reads
2009-03-05
3,683 reads
Using NOLOCK and READPAST table hints in SQL Server
Table locking hints provide developers much tighter control of their transactions. Look at the benefits and disadvantages of using the NOLOCK and READPAST table hints in SQL Server
2008-07-15
5,492 reads
Blogs
Did You Really Name That Default?
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
Monday Monitor Tips: A New Analysis Page
By Steve Jones
We have multiple teams (8) working on Redgate Monitor. Some work on the Standard...
Case Studies: Real-World Success Stories of FinOps Implementation
By HeyMo0sh
Learning any kind of theory is easy, but adapting FinOps and watching it rescue...
Forums
The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI
Comments posted to this topic are about the item The day-to-day pressures of a...
The Problem Isn't Always Your Query or Schema... Sometimes It's Hidden Assumptions
Comments posted to this topic are about the item The Problem Isn't Always Your...
Identity Defaults
Comments posted to this topic are about the item Identity Defaults
Question of the Day
Identity Defaults
What happens when I run this code?
CREATE TABLE dbo.IdentityTest
(
id int IDENTITY(10) PRIMARY KEY,
somevalue VARCHAR(20)
)
GO
See possible answers