What is the advantage of using FAST_FORWARD for defining a cursor? Is it better for performance? why?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What is the advantage of using FAST_FORWARD for defining a cursor? Is it better for performance? why?
The definition from MSDN is:
I’ve boldened the key bit. It can support these “performance optimisations” because it does not need to support multi-direction iterating through the cursor (FORWARD_ONLY) and does not support modifications (READ_ONLY).
Of course, if you don’t really need to use a cursor at all – then using a cursor even with this option is not going to perform as well . If you can do the same task using a set-based approach, do that instead – this is the bit I really wanted to stress.