Let me put this another way - maybe this will help ...
The following SQL selects the *opposite* of what I want to do with the SQL in my original post:
CYCLE.CY_CYCLE_ID AS "Test Set ID",
CYCLE.CY_CYCLE AS "Test Set Name",
CYCL_FOLD.CF_ITEM_NAME AS "Test Set Folder",
TEST.TS_USER_04 AS "Test Functional Area",
TEST.TS_TEST_ID AS "Test ID",
TEST.TS_NAME AS "Test Name",
REQ.RQ_REQ_ID AS "Req ID",
REQ.RQ_REQ_NAME AS "Req Name"
FROM REQ, REQ_COVER, TEST, TESTCYCL, CYCLE, CYCL_FOLD
REQ.RQ_REQ_ID = REQ_COVER.RC_REQ_ID
AND TEST.TS_TEST_ID = REQ_COVER.RC_ENTITY_ID
AND TESTCYCL.TC_TEST_ID = TEST.TS_TEST_ID
AND TESTCYCL.TC_CYCLE_ID = CYCLE.CY_CYCLE_ID
AND CYCLE.CY_FOLDER_ID = CYCL_FOLD.CF_ITEM_ID
AND REQ.RQ_REQ_ID IS NOT NULL
ORDER BY CYCLE.CY_CYCLE_ID
This returns a row for every Test in a Test Set that has a linked Requirement.
I originally thought taking the "NOT" out of the last statement in the WHERE clause would do it:
AND REQ.RQ_REQ_ID IS NULL
... but this returns no rows. I think the SQL Chandu posted for me does essentially the same thing as what I just described with taking the "NOT" out.
I tried using LEFT JOIN (see the SQL in my original post) but that was giving me an error.
Still at a loss.