See SQL Books Online for a full explanation, but think of it as a pointer to
a set of rows that depending on the options called can move forwards or
backwards through the set.
In general, cursors are an inefficient last ditch effort that should be
avoided for both performance and locking reasons. TSQL is a set oriented
language and again another generality when coded in a set oriented way will
out perform row oriented approaches.
The SQL group in this news group is pretty good about helping out if you
post an explanation of the issue, the object creation, and data insert
scripts for testing.
Danny
"Tyler H." <se************@resonant.com> wrote in message
news:53**************************@posting.google.c om...
I had a friend write a stored procedure to perform a function for one
of my clients. What he wrote doesn't fully do what I need, and I hope
to finish it myself. I have programming sense, but not so much with
SQL.
I'm trying to figure out the code, and he has used something called a
"cursor." I'm not sure whether this is an SQL construct or a structure
that he has just labeled "cursor." My guess is that it is an SQL
construct. Can anyone give me a quick run down of how this works?
sincerely,
Tyler H.
-----------------------------------------------
<a href="http://www.seearoomhawaii.com/bed-breakfasts/">bed &
breakfasts in Hawaii</a>