Re: Opening cursor after closing does not seem to requery
From: mberry (lionheart1159_at_yahoo.com)
Date: 03/12/04
- Next message: JT Lovell: "Re: Comma delimited issues"
- Previous message: Lee: "Select statment"
- In reply to: David Portas: "Re: Opening cursor after closing does not seem to requery"
- Next in thread: David Portas: "Re: Opening cursor after closing does not seem to requery"
- Reply: David Portas: "Re: Opening cursor after closing does not seem to requery"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 12 Mar 2004 13:04:33 -0500
Thanks for the quick response, David. I would very much like to have a
set-based alternative, and I will attempt to scale my code down so I can
post a sample of what I am attempting to do. However, for now: is it true
that when I close a cursor (but not deallocate), then open it again, it
should re-execute the query defined in the declare statement?
Thanks again,
Michael
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@acm.org> wrote in message
news:GeKdnZK1oPl3cszdRVn-gw@giganews.com...
> > parse through the table, doing stuff that could probably be done
> > easier with correlated subqueries
>
> You said it! Why don't you post the DDL and the code and maybe someone can
> give a solution that doesn't require a cursor at all. A cursor should be a
> last resort if there are set-based alternatives.
>
> --
> David Portas
> SQL Server MVP
> --
>
>
- Next message: JT Lovell: "Re: Comma delimited issues"
- Previous message: Lee: "Select statment"
- In reply to: David Portas: "Re: Opening cursor after closing does not seem to requery"
- Next in thread: David Portas: "Re: Opening cursor after closing does not seem to requery"
- Reply: David Portas: "Re: Opening cursor after closing does not seem to requery"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|