Stairway to Advanced T-SQL

Stairway to Advanced T-SQL Level 4: Record Level Processing Using Transact-SQL Cursors

Using a CURSOR is not normally the best way to process through a set of records. Yet when a seasoned programmer moves to writing TSQL for the first time they frequently look for ways to process a sets of records one row at a time. They do this because they are not used to thinking about processing records as a set. In order to process through a TSQL record set a row at a time you can use a cursor. A cursor is a record set that is defined with the DECLARE CURSOR statement. Cursors can be defined as either read-only or updatable. In this article I will introduce you to using cursors to do record level processing one row at a time.

SQLServerCentral Editorial

To Each Their Own

I recently came back from a trip to Las Vegas. I was privileged to be able to take part in the very first Fabric Community Conference. It was a great event, well attended. BUT... It was in Las Vegas. I am not a fan. First of all, Vegas is just far too noisy for me. […]

Blogs

Stupid Things I Did With AI: ASCII Art

By

I ran across this article recently (https://www.gatesnotes.com/meet-bill/source-code/reader/microsoft-original-source-code) and it has a great opening piece...

Simple Talks Podcasting in 2026

By

I’m in the UK today, having arrived this morning in London. Hopefully, by this...

SSMS 22 still inserting tabs instead of spaces

By

I’m not trying to start up a debate whether you should use tabs or...

Read the latest Blogs

Forums

Cumulative Update 23 - KB5074819 - Database Mail - No longer working.

By ChrisRNZ

Hi there, Has anyone else had any trouble with Database Mail in Cumulative Update...

Script Task execution error with HTTP request

By Bhagat

I have a script task that tries to execute a HTTP request, which seems...

SQL Server 2025 Standard Developer Edition

By Johan Bijnens

Comments posted to this topic are about the item SQL Server 2025 Standard Developer...

Visit the forum

Question of the Day

URL Safe or Not?

If I use BASE4_ENCODE() in SQL Server 2025, is the output URL Safe by default?

See possible answers