SQL SERVER – Tips from the SQL Joes 2 Pros Development Series – Finding un-matching Records – Day 5 of 35

Answer simple quiz at the end of the blog post and –
Every day one winner from India will get Joes 2 Pros Volume 1.
Every day one winner from United States will get Joes 2 Pros Volume 1.

Finding un-matching Records

Often time we want to find records in one table that have no matching key in another table. This is common for things like finding products that have never sold, or students who did not re-enroll. Something we were expecting is missing. Records in one table were expecting some related activity in another table and did not find them. There are many ways to find these records.

Basic Subquery

We have probably all heard that subqueries should be avoided if there is a better solution. Often times basic subqueries are used where a simple “Unmatched Records Query” could have been used.

Let’s start off with the subquery example. Looking at the Location table in the figure below we see all the data. In fact, this table does not allow nulls for the LocationID field. Looking further, there are no nulls anywhere in the Location table. So does this mean that all locations have at least one employee? It’s possible that some of these locations might be new and have not employees working there yet.

SQL SERVER - Tips from the SQL Joes 2 Pros Development Series - Finding un-matching Records - Day 5 of 35 j2p_5_1

How can we find the location with no employees. We can use a subquery. For example we can use the following query to find all locations of the JProCo database that have now employee working there.

SELECT *
FROM Location
WHERE LocationID
NOT IN (SELECT DISTINCT LocationID
FROM Employee
WHERE LocationID IS NOT NULL)

Unmatched Records Queries

If you wanted to find all locations with no employees, you could run an “Unmatched Records Query”. Let’s build this piece by piece. In this case, we have to join the Location table with the Employee table to determine the location that has no employees. What type of join will tell us this? Since nulls don’t map through a join, the INNER JOIN drops the record from the result set and we won’t see Chicago. The outer join will show both the matches and the unmatched records, so we see every location. In the figure below we get all location even if there are no employees.

Notice Seattle is listed many times but Chicago is listed once with no employees found. A NULL appears in the fields from the Employee table for Chicago. With the Location table on the left and the NULL on the right, we have part of an unmatched records query. To find just the records that don’t match, we look for null records on the table that the outer join does not favor. In this case, it’s the Employee table.

SQL SERVER - Tips from the SQL Joes 2 Pros Development Series - Finding un-matching Records - Day 5 of 35 j2p_5_2

The outer join will show us the unmatched records with null location details if you set the WHERE clause to look for nulls on a field in the non-dominant table. Unmatched record queries use SQL to return a result set displaying only the unmatched records between the two tables.

When our query criterion specifies NULL, only Chicago shows up in our result set. By doing a LEFT OUTER JOIN and using a NULL value from the Employee table (or “RIGHT” table) as our search condition criteria, our unmatched records query shows us one record.

SQL SERVER - Tips from the SQL Joes 2 Pros Development Series - Finding un-matching Records - Day 5 of 35 j2p_5_3

Note: If you want to setup the sample JProCo database on your system you can watch this video.

Question 5

Q 5) Which of the following queries will show all location that have no employees?

  1. SELECT P.EmployeeID, T.[Name] FROM Employee P LEFT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE T.TerritoryID IS NULL
  2. SELECT P.EmployeeID, T.[Name] FROM Employee P LEFT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE P.TerritoryID IS NULL
  3. SELECT P.EmployeeID, T.[Name] FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE T.TerritoryID IS NULL
  4. SELECT P.EmployeeID, T.[Name] FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE P.TerritoryID IS NULL

Please post your answer in comment section to win Joes 2 Pros books.

Rules:

Please leave your answer in comment section below with correct option, explanation and your country of resident.
Every day one winner will be announced from United States.
Every day one winner will be announced from India.
A valid answer must contain country of residence of answerer.
Please check my facebook page for winners name and correct answer.
Winner from United States will get Joes 2 Pros Volume 1.
Winner from India will get Joes 2 Pros Volume 1.
The contest is open till next blog post shows up at which is next day GTM+2.5.

Reference:  Pinal Dave (https://blog.sqlauthority.com)

Joes 2 Pros, SQL Scripts
Previous Post
SQL SERVER – Tips from the SQL Joes 2 Pros Development Series – Efficient Query Writing Strategy – Day 4 of 35
Next Post
SQL SERVER – Row Constructors – Day 6 of 35

Related Posts

135 Comments. Leave new

  • Jagdish Prajapati
    August 5, 2011 3:44 pm

    Hi All
    Ans # 4 is right

    Ahmedbad-INDIA

    Reply
  • Raghavendra Raju
    August 5, 2011 3:46 pm

    Answer : 4
    Country : India

    Reply
  • Option 4 is the correct one.

    Country India

    Reply
  • sachin kulshreshtha
    August 5, 2011 4:03 pm

    Answer is: 4

    4. SELECT P.EmployeeID, T.[Name]
    FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE P.TerritoryID IS NULL

    Country : india

    Reply
  • The correct option is 4.

    SELECT P.EmployeeID, T.[Name]
    FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE P.TerritoryID IS NULL

    Country: India

    Varun

    Reply
  • Answer: Option 4
    Because Employee table is Right Outer Join with Location Table and having a condition on territory Id from Employee table which is nothing but the Location table is left outer join with Employee table and territory is null in employee table.

    India

    Reply
  • Answer: Option 4

    SELECT P.EmployeeID, T.[Name]
    FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE P.TerritoryID IS NULL
    Country: India(sikha)

    Reply
  • abhishek mishra
    August 5, 2011 5:16 pm

    Answer 4 is correct answer

    Reply
  • Mandar Alawani
    August 5, 2011 5:20 pm

    Correct answer :
    Option 4:
    SELECT P.EmployeeID, T.[Name]
    FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE P.TerritoryID IS NULL

    Thanks,
    Mandar
    Mumbai,INDIA

    Reply
  • abhishek mishra
    August 5, 2011 5:21 pm

    Answer 4 is correct answer

    Abhishek Mishra
    Country India

    Reply
  • Option 4 is the correct Answer

    4.SELECT P.EmployeeID, T.[Name]
    FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE P.TerritoryID IS NULL

    Country: INDIA

    Reply
  • Question 5

    Q 5) Which of the following queries will show all location that have no employees?

    Answer:

    4.SELECT P.EmployeeID, T.[Name]
    FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE P.TerritoryID IS NULL

    Answerer: Sivaprasad S

    Country: India

    Reply
  • The correct answer is:

    4.SELECT P.EmployeeID, T.[Name]
    FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE P.TerritoryID IS NULL

    Country: United States

    Reply
  • Mike Michalicek
    August 5, 2011 5:58 pm

    The correct answer is #4

    USA

    Mike Michalicek

    Reply
  • Anish Shenoy.P
    August 5, 2011 6:19 pm

    Hi Pinal Dev,

    The correct answer is Option 4,

    SELECT P.EmployeeID, T.[Name]
    FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE P.TerritoryID IS NULL

    The First two option is Left Outer join which is an invalid answer for the question as the Territory Id will never be shown up when we do a left outer join.

    And the 3 Option is trying to find where TerritoryId is null in the location table which is not possible as Location is the master table.

    P.Anish Shenoy
    INDIA, Bangalore Karnataka

    Reply
  • DiveSh Singhvi
    August 5, 2011 6:36 pm

    4. SELECT P.EmployeeID, T.[Name]
    FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE P.TerritoryID IS NULL

    Divesh
    INDIA

    Reply
  • Hiren Bavishi
    August 5, 2011 6:41 pm

    Correct answer is option 4

    SELECT P.EmployeeID, T.[Name]
    FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE P.TerritoryID IS NULL

    RIGHT OUTER JOIN will give all the records from location table and matching records from employee table. Where condition will filter data from employee table and result will be locations which are not in employee table.

    Hiren Bavishi
    India

    Reply
  • Himanshu Patel
    August 5, 2011 6:41 pm

    3. SELECT P.EmployeeID, T.[Name]
    FROM Employee P RIGHT OUTER JOIN Location T
    ON T.TerritoryID = P.TerritoryID
    WHERE T.TerritoryID IS NULL

    Reply
  • correct answer is 4
    India

    Reply
  • answer-4

    Reply

Leave a Reply