Results 1 to 4 of 4

Thread: Cursor question

  1. #1
    Join Date
    Feb 2004
    Posts
    86

    Unanswered: Cursor question

    Is there a limit to the amount of rows returned using a cursor. E.g. if the cursor was to return 1 million rows, what are the performance issues?

  2. #2
    Join Date
    Jul 2003
    Posts
    2,296
    depends on what you are doing with the data the cursor retrieves.

    in general, it would perform similar to a standard select statement except
    it doesn't have to spit all the data out the the screen.

    whatever the plan and stats on a query will generally be the same for the cursor.
    - The_Duck
    you can lead someone to something but they will never learn anything ...

  3. #3
    Join Date
    Aug 2003
    Location
    Where the Surf Meets the Turf @Del Mar, CA
    Posts
    7,776
    Provided Answers: 1
    >if the cursor was to return 1 million rows, what are the performance issues?
    Network bandwidth between DB server & client.
    You can lead some folks to knowledge, but you can not make them think.
    The average person thinks he's above average!
    For most folks, they don't know, what they don't know.
    Good judgement comes from experience. Experience comes from bad judgement.

  4. #4
    Join Date
    May 2004
    Location
    Dominican Republic
    Posts
    721
    Quote Originally Posted by anacedent
    >if the cursor was to return 1 million rows, what are the performance issues?
    Network bandwidth between DB server & client.
    Actually, all that I thought it was that a cursor is actually a pointer to the select statement you made it for, being this a row by row operation.

    So I back up what The_Duck said about:

    "in general, it would perform similar to a standard select statement except
    it doesn't have to spit all the data out the the screen"

    Corrections welcomed!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •