You can create a left outer join with a join override. You can enter multiple left outer joins in a single join override. When using left outer joins with other joins, list all left outer joins together, after any normal joins in the statement. 
To create a left outer join, use the following syntax: 
{ 
source1
LEFT OUTER JOIN
source2
on
join_condition
 }
The following tables displays syntax for left outer joins in a join override: 
    
  
      
|  | Source resource name. With a left outer join, the Data Integration Service returns all rows in this resource.  | 
|  | Source resource name. The Data Integration Service returns rows from this resource that match the join condition.  | 
|  | Condition for the join. Use syntax supported by the source database. You can combine multiple join conditions with the AND operator.  | 
 
 
  
  
For example, using the same REG_CUSTOMER and PURCHASES tables described in 
Normal Join Syntax, you can determine how many customers bought something in June with the following join override: 
{ REG_CUSTOMER LEFT OUTER JOIN PURCHASES on REG_CUSTOMER.CUST_ID = PURCHASES.CUST_ID }
The Data Integration Service returns the following data: 
The Data Integration Service returns all registered customers in the REG_CUSTOMERS table, using null values for the customer who made no purchases in June. It does not include purchases made by non-registered customers. 
Use multiple join conditions to determine how many registered customers spent more than $100.00 in a single purchase in June: 
{REG_CUSTOMER LEFT OUTER JOIN PURCHASES on (REG_CUSTOMER.CUST_ID = PURCHASES.CUST_ID AND PURCHASES.AMOUNT > 100.00) }
The Data Integration Service returns the following data: 
You might use multiple left outer joins if you want to incorporate information about returns during the same time period. For example, the RETURNS table contains the following data: 
To determine how many customers made purchases and returns for the month of June, use two left outer joins: 
{ REG_CUSTOMER LEFT OUTER JOIN PURCHASES on REG_CUSTOMER.CUST_ID = PURCHASES.CUST_ID LEFT OUTER JOIN RETURNS on REG_CUSTOMER.CUST_ID = PURCHASES.CUST_ID }
The Data Integration Service returns the following data: 
The Data Integration Service uses NULLs for missing values.