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 Article

SQL Server 2022 Build List

This is a list of the builds for SQL Server 2022. There are other build lists available here. A list of all the builds that I can find and install on my Build VM. If you find a build not listed here, please let the webmaster know (webmaster at sqlservercentral.com). All builds are listed in reverse […]

Blogs

A New Word: the Wends

By

the wends– n. the frustration that you’re not enjoying an experience as much as...

7 Best Online Advanced SQL Training Courses to Learn in 2024 and Beyond

By

The world runs on data, and SQL is the key to unlocking its secrets....

Manually Updating Redgate Monitor/SQL Monitor Patch Info

By

This post looks at updating the patch information for SQL Monitor/Redgate Monitor without using...

Read the latest Blogs

Forums

There's No Free Lunch with Open-source Software

By Ryan Booz

Comments posted to this topic are about the item There's No Free Lunch with...

Upgrading SSRS 2016 to SSRS 2019 in place

By koln

Server A has SSRS 2016 on it and I would now like to upgrade...

Pipeline Failure Route not working

By rjdineen

Hi there, I have a couple of Stored Proc tasks, that fire off after...

Visit the forum

Question of the Day

Default Objects in Clones

On SQL Server 2022, I do this:

USE model
GO
CREATE TABLE dbo.DBALog
(logdate DATETIME2(3), logmsg VARCHAR(2000))
GO
I then create a new database:
CREATE DATABASE INVENTORY
GO
I install a new database application in here with multiple tables, views, etc. I do not run any queries. I then decide to run this code:
DBCC CLONEDATABASE(INVENTORY, Inventory_clone);
GO
What happens?

See possible answers