Re: Bizarre scenario solved by READWRITE clause on end of SELECT SQL

On 6/24/2020 5:35 PM, Richard Kaye wrote:

If you don't need the overhead of a writable cursor you can also use NOFILTER to force the query engine to not just do a USE...AGAIN with a filter. As for why now, the simplest answer I can think of is there was something about the query and the source data where Rushmore decided the latter strategy was the best way to give the desired results.

I've honestly never used the NOFILTER clause.  How much overhead does READWRITE cause vs. the NOFILTER I wonder?  Are we again talking about something negligible?