I'd tend to move the update outside of the loop in order to maximize SQL since that's the most efficient way to process data.If your business logic is amenable to it, I'd also suggest doing bulk operations to fetch the data into local collections that your business logic can iterate through in order to minimize context shifts between SQL and PL/SQL. LAST LOOP IF( l_modified_employees(i).status = 'Active' ) THEN -- Custom logic 1 ELSE -- Custom logic 2 END IF; END LOOP; END; Justin the table employee has processed and non processed records and the only way to know this is by the fact that non processed records have a status of null.So, based on your comments, in your example, there should be a predicate in the definition of your cursor, right? DECLARE CURSOR cur IS SELECT emp_no, status FROM employee WHERE status IS NULL; TYPE l_employee_array IS TABLE OF cur%rowtype; l_modified_employees l_employee_array; BEGIN UPDATE employee e SET status = (select es.status from employee_status es where es.emp_no = e.emp_no) WHERE status IS NULL AND EXISTS (SELECT 1 FROM employee_status es WHERE es.emp_no = e.emp_no) RETURNING emp_no, status BULK COLLECT INTO l_modified_employees; FOR i IN l_modified_employees. So I only need to update and then subsequently process those records and not the rest.

plsql updating in cursor-49

Once I have done this I need to use this status for calling custom business logic and not the original status retrieved by the cursor. Emp_No; IF(v_status = 'Active') THEN -- Custom Business Logic ELSE -- Business logic END IF; END LOOP; clause are released and other sessions are free to update the same rows.

In later versions of Oracle, you'll get an "ORA-01002: fetch out of sequence" if you do this.

In earlier versions of Oracle, this error was ignored which lead to occasionally incorrect results.

2) Do you need to update the table on a row-by-row basis?

FOR Rec IN Cur LOOP SELECT a.status INTO v_status from Employee_Status a where a.

Anytime you can process by using the row rowid in an Oracle table you will get the best performance. Time reductions for some massive UPDATEs were reduced from 12-13 hours to 6 or less as reported by several sites using ROWID processing. Implicit type conversions result in the statement not being able to use indexes thus forcing a full table scan.

By combining bulk bind and ROWID even greater improvements should be realized. (to use John Beresniewicz's technical terminology) through the table or tables committing, releasing cursors then resuming where we left off. Always use %TYPE and %ROWTYPE to capture the types from either the specific table or cursor being used.

Each time, ANSI added new features and incorporated new commands and capabilities into the language.remove all records from a table, including all spaces allocated for the records are removed (It is fast as compared to Delete and does not generate undo information as Delete does.

ANSI released updates in 1992, known as SQL92 and SQL2, and again in 1999, termed both SQL99 and SQL3.