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,118 reads
Isolation Levels
2012-11-21
2,105 reads
2012-04-19
2,012 reads
2010-07-06
3,085 reads
2009-03-19
3,973 reads
2009-03-05
3,682 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
Using CAT for Testing of Data Agents
In last months one of the scenarios where you can use AI has been...
Are you getting value from your reporting?
By ChrisJenkins
Do you spend so long manipulating your data into something vaguely useful that you...
The Book of Redgate: SQL Server Central
By Steve Jones
It was neat to stumble on this in the book, a piece by me,...
Forums
Foreach Loop still executes after process and delete all the folders
I have two challenges XML source control not displaying the XML file parent node...
Which 'Where' statement conditional upon a variable
Thanks in advance for any clues on this. I am trying to write a...
Backup to Immutable Storage
Comments posted to this topic are about the item Backup to Immutable Storage
Question of the Day
Backup to Immutable Storage
In SQL Server 2025, a backup can be made on Azure Immutable Storage. What changes in how the backup is created?
See possible answers