• Hi All

    I agree that you can run into problems when using cursors without thought

    However I have an instance where I have to gather information from a 3.2 billion row partioned table. The table is partioned on website_id

    and table houses keyword data by page.

    I have to pull information out of this table for potentially thousands of websites and if I do it set-based it takes a large amount of time

    I changed to use a cursor as the speed of the retrieval of this information was cut by 50 times when using a cursor which was a massive saving and allowed people to use the report it was intended for

    So I gues what I am saying is that its all good and fine to bash cursors but would it not be fair to conceed that there is a place for cursors?

    And if you are adament that cursors should never be used I will be happy to use my example as a proper production test case to be proved wrong

    thanks

    Chris