The NOT IN and NOT LIKE operators are also known as the SQL NOT IN and NOT LIKE operators. These operators are not normally very selective and are often very costly operation-wise in direct SQL.
Avoid all constructs on the A.60.06 screen that are known to be potential performance bottlenecks in direct SQL. If you are unsure, have your DBA check the created query with the EXPLAIN plan tool. Often, a costly construct can be substituted with an equivalent construct that provides much better performance.
If a complicated selection criteria must be used, a knowledgeable SQL user can enter a SQL query directly on the A.60.06 screen by clearing the Regenerate check box.
Clearing the Regenerate check box and entering complicated SQL selection criteria should only be used as a
last resort.