Scope of Cursors in Stored Procedures 1

[gradley]

I ran into a situation this morning that I didn't know was possible. I executed a stored procedure which contained cursor processing. During the process, I trapped for a situation and exited the stored procedure without closing and deallocating the cursor.

When I called the stored procedure a second time, I received a "A cursor with the name curEmployeeFK already exists" message.

My previous assumption was that everything in Stored Procedures was local to the procedure. Can anyone shed some light on why this happens?

 

[dbomrrsm]

dont know why it happens but my understanding was that nothing except a close and deallocate command will end a cursor.

[blue]DBomrrsm[/blue]

 

[dbomrrsm]

Furthermore - when you close a cursor it still remains available for use by issuing an open command - it is only when it is deallocated that it becomes unavailable.

[blue]DBomrrsm[/blue]