In my T-SQL code I always use set based operations.
I have been told these types of operations are what SQL Server is designed to process and it should be quicker than serial processing. I assume Microsoft created them for a reason so they must have a place where they can be used in an efficient manner.
Regardless of your stand on cursors they probably have a place in particular circumstances and not in others.
So it boils down to your understanding of the coding technique then your understanding of the problem at hand to make a decision on whether or not cursor based processing is appropriate or not.
To get started let's do the following: Since 2002, Jeremy Kadlec has delivered value to the global SQL Server community as an Edgewood Solutions SQL Server Consultant, co-founder and Baltimore SSUG co-leader.
Individual virtual table implementations might impose additional constraints.
For example, some virtual implementations might provide read-only tables.
Or some virtual table implementations might allow INSERT or DELETE but not UPDATE.
Or some virtual table implementations might limit the kinds of UPDATEs that can be made.
A virtual table might represent an in-memory data structures.
Or it might represent a view of data on disk that is not in the SQLite format.