Cursor in SQL server?

Question

5.00/5 (1 vote)

See more:

hi friends,

--OPEN CURSOR:

OPEN @getid

FETCH ROW FROM THE CURSOR

FETCH NEXT

FROM @getid INTO @id

WHILE @@FETCH_STATUS

BEGIN

PRINT @id

FETCH NEXT

FROM @getid INTO @id

END

--CLOSE CURSOR

CLOSE @getid

--DE-ALLOCATED CURSOR

DE-ALLOCATED @getid

i have doubt in while condition like while @@fetch_status
why we are using global variable there? any one clarify my doubt?

Posted 14-Dec-12 0:46am

leosang

Add a Solution

Comments

StackQ 14-Dec-12 7:11am

gud question.I also want to know?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Stephen Hewison · Answer 1 · 2012-12-14T03:08:00

I'm not sure as to why it uses a global variable but here are my thoughts on the subject.

"@@FETCH_STATUS is global to all cursors on a connection"

http://msdn.microsoft.com/en-us/library/ms187308.aspx[^]

This means that you do have to be aware of the behaviour such variable type. You can create a problem if your cursor calls a stored procedure which implements another cursor as the @@FETCH_STATUS value will be invalid when returning from the stored procedure. The trick is to make sure you always evaluate the result of a fetch immediately after executing the fetch.

But as is often the way, you can do things a number of ways. You can check the fetch_status of any given cursor using the sys.dm_exec_cursors management function.

Read here for more details on this function.

http://msdn.microsoft.com/en-us/library/ms190346.aspx[^]