Databases
StackOverflow2013
Postsdbo
POFull outer join not returning all rows?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POFull outer join not returning all rows?
    primarykey
    data
    text
    <p>I have a table that contains multiple records for multiple dates.</p> <p>I am trying to see the difference between "date 1" and "date 2" and my full outer join is not returning the data I was expecting.</p> <p>I know there are 13278 rows on date 1 and 13282 on date 2 - therefore I would expect to see at least 13282 rows, but I get back 13195...which is an <code>INNER JOIN</code> (I tested this).</p> <p>I am hoping for results like:</p> <pre><code>001 000123 009 NULL 1000 001 000124 009 1000 1000 001 000125 009 1000 1000 001 000126 009 1000 NULL </code></pre> <p>but this don't get any of the null rows from either side?</p> <pre><code>SELECT COALESCE(c.AccountBranch, p.AccountBranch) , COALESCE(c.AccountNumber, p.AccountNumber) , COALESCE(c.AccountSuffix, p.AccountSuffix) , c.PrincipleAmount , p.PrincipleAmount FROM ADStaging..cb_account_extension_principle_dpd c FULL OUTER JOIN ADStaging..cb_account_extension_principle_dpd p ON p.AccountBranch = c.AccountBranch AND p.AccountNumber = c.AccountNumber AND p.AccountSuffix = c.AccountSuffix WHERE (c.BusinessDataDate IS NULL OR c.BusinessDataDate = @CurrentBusinessDataDate) AND (p.BusinessDataDate IS NULL OR p.BusinessDataDate = @PreviousBusinessDataDate) </code></pre> <hr> <p>This works - combining the "key" for the join in two separate select statements?</p> <pre><code>SELECT COALESCE(C.Account, P.Account) AS Account , COALESCE(C.AccountBranch, P.AccountBranch) as AccountBranch , COALESCE(C.AccountNumber, P.AccountNumber) as AccountNumber , COALESCE(C.AccountSuffix, P.AccountSuffix) as AccountSuffix , P.PrincipleAmount AS PreviousAmount , C.PrincipleAmount AS CurrentAmount , ISNULL(C.PrincipleAmount, P.PrincipleAmount) - ISNULL(P.PrincipleAmount,0) FROM (SELECT (pd.AccountBranch + pd.AccountNumber + pd.AccountSuffix) AS Account , pd.AccountBranch , pd.AccountNumber , pd.AccountSuffix , pd.PrincipleAmount FROM ADStaging..cb_account_extension_principle_dpd pd WHERE pd.BusinessDataDate = @CurrentBusinessDataDate) C FULL OUTER JOIN (SELECT (pd.AccountBranch + pd.AccountNumber + pd.AccountSuffix) AS Account , pd.AccountBranch , pd.AccountNumber , pd.AccountSuffix , pd.PrincipleAmount FROM ADStaging..cb_account_extension_principle_dpd pd WHERE pd.BusinessDataDate = @PreviousBusinessDataDate) P ON P.Account = C.Account WHERE (P.PrincipleAmount IS NULL OR C.PrincipleAmount IS NULL) OR P.PrincipleAmount &lt;&gt; C.PrincipleAmount </code></pre> <hr> <p>But this doesn't - joining on the combined values - only when they are separate tables?</p> <pre><code>SELECT COALESCE(c.AccountBranch, p.AccountBranch) , COALESCE(c.AccountNumber, p.AccountNumber) , COALESCE(c.AccountSuffix, p.AccountSuffix) , c.PrincipleAmount , p.PrincipleAmount FROM ADStaging..cb_account_extension_principle_dpd c FULL OUTER JOIN ADStaging..cb_account_extension_principle_dpd p ON (p.AccountBranch + p.AccountNumber + p.AccountSuffix) = (c.AccountBranch + c.AccountNumber + c.AccountSuffix) WHERE (c.BusinessDataDate = @CurrentBusinessDataDate) AND (p.BusinessDataDate = @PreviousBusinessDataDate) </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBlueChippy
    1. USBlueChippy
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COExecution plan shows this as running an INNER JOIN??? Now very confused!
      singulars
      1. POFull outer join not returning all rows?
      1. USBlueChippy
    2. COA condition in the where kills an outer join.
      singulars
      1. POFull outer join not returning all rows?
      1. USpaparazzo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload