Often code can be re-written in a set based manner (i.e. If you're adamant you want to perform an RBAR operation (simple-talk.com/sql/t-sql-programming/…) then a cursor is the thing you want to investigate.Perhaps you can explain what you will be doing with this data in more detail.In the online version (which also matches the quiz offered at PL/SQL Challenge, both a and b are correct.Visit PL/SQL Challenge to read a complete explanation of the answers to this quiz. If the SELECT statement identifies more than one row to be fetched, Oracle Database will raise the TOO_MANY_ROWS exception.In each of these camps they have different reasons for their stand on cursor usage.Regardless of your stand on cursors they probably have a place in particular circumstances and not in others.This article focuses on the most-common ways programmers execute SELECT statements in PL/SQL, namely At the end of the article, I offer some quick tips to help you figure out which of these techniques you should use for different scenarios.
Next, we'll declare our cursor, open it and move it to the first record.
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.
I know cursors exist but I am not sure how to use them. In some circles cursors are never used, in others they are a last resort and in other groups they are used regularly.
A cursor is a pointer to a private SQL area that stores information about the processing of a SELECT or data manipulation language (DML) statement (INSERT, UPDATE, DELETE, or MERGE).
Cursor management of DML statements is handled by Oracle Database, but PL/SQL offers several ways to define and manipulate cursors to execute SELECT statements.