2025-09-03
1,921 reads
cursors
A Case FOR Cursors...
We've all heard that definitive statement: "Avoid using cursors." But, in my opinion, what really should be conveyed is: "Avoid using row-by-row operations when possible."
2016-09-09 (first published: 2015-06-01)
13,572 reads
Performance Improvement for Cursors in Stored Procedures
Exploring some differences between using cursors, local fast forward cursors and using set logic.
2016-11-11 (first published: 2015-02-03)
17,360 reads
Cursor-Killing: Retrieving Recently Modified Data
Cursors are considered by many to be the bane of good T-SQL. What are the best ways to avoid iterative T-SQL and to write queries that look and perform beautifully? In the next part of an ongoing series, we look at ways to efficiently retrieve recently modified data.
2014-06-02
7,060 reads
A simple T-SQL statement to create a list of lookup values
In this article, we provide a simple way to get a comma delimited list from a table of entries without having to use a CURSOR or a WHILE loop to read through the table.
2012-09-28 (first published: 2011-03-21)
34,387 reads
What Every DBA Ought to Know About SQL Server Cursors (and Their Alternatives)
Cursors provide a means of processing through a set of records row-by-row. However, many companies have a policy against using cursors in their SQL Server standards. This article examines the problem with cursors and alternatives to using them.
2010-09-01
5,122 reads
4 Ways to Increase Your Salary (Using UPDATE)
This article depicts how to approach row by row updates needed in a salary table. It might not directly let you increase your salary, but it could help you at review time.
2009-11-26
42,869 reads
Avoiding cursors with SQL Server 2005
Sometimes cursors are necessary when executing queries in SQL Server, but most of the time they can be avoided entirely. This article shows where cursors can traditionally be used, and how you can use features packaged in SQL Server 2005 to avoid them.
2009-03-19
5,627 reads
Cursors for T-SQL Beginners
Should we really avoid cursors? See how to rewrite code to avoid cursors and also analyze the implications.
2011-05-27 (first published: 2009-01-01)
23,283 reads
2010-06-23 (first published: 2008-12-24)
37,401 reads
Blogs
Why Optimize CPU for RDS SQL Server is a game changer
One feature that I have been waiting for years! The new announcement around optimize...
Performance tuning KubeVirt for SQL Server
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
T-SQL Tuesday #193 – A Note to Your Past, and a Warning from Your Future
By DesertDBA
I haven’t posted in a while (well, not here at least since I’ve been...
Forums
Refactoring SQL Code
Comments posted to this topic are about the item Refactoring SQL Code, which is...
The Read Committed Snapshot Isolation behaviour
Comments posted to this topic are about the item The Read Committed Snapshot Isolation...
Working with JSON/JSONB Data in PostgreSQL using Python
Comments posted to this topic are about the item Working with JSON/JSONB Data in...
Question of the Day
The Read Committed Snapshot Isolation behaviour
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers