Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Working with Transformations
  3. Aggregator Transformation
  4. Classifier Transformation
  5. Cleanse transformation
  6. Comparison Transformation
  7. Custom Transformation
  8. Custom Transformation Functions
  9. Consolidation Transformation
  10. Data Masking Transformation
  11. Data Masking Examples
  12. Decision Transformation
  13. Dynamic Lookup Cache
  14. Expression Transformation
  15. External Procedure Transformation
  16. Filter Transformation
  17. HTTP Transformation
  18. Identity Resolution Transformation
  19. Java Transformation
  20. Java Transformation API Reference
  21. Java Expressions
  22. Java Transformation Example
  23. Joiner Transformation
  24. Key Generator Transformation
  25. Labeler Transformation
  26. Lookup Transformation
  27. Lookup Caches
  28. Match Transformation
  29. Match Transformations in Field Analysis
  30. Match Transformations in Identity Analysis
  31. Merge Transformation
  32. Normalizer Transformation
  33. Parse transformation
  34. Rank Transformation
  35. Router Transformation
  36. Rule Specification transformation
  37. Sequence Generator Transformation
  38. Sorter Transformation
  39. Source Qualifier Transformation
  40. SQL Transformation
  41. Using the SQL Transformation in a Mapping
  42. Stored Procedure Transformation
  43. Standardizer Transformation
  44. Transaction Control Transformation
  45. Union Transformation
  46. Unstructured Data Transformation
  47. Update Strategy Transformation
  48. Verifier transformation
  49. Weighted Average Transformation
  50. XML Transformations

Transformation Guide

Transformation Guide

Informatica Join Syntax

Informatica Join Syntax

When you enter join syntax, use the Informatica or database-specific join syntax. When you use the Informatica join syntax, the Integration Service translates the syntax and passes it to the source database during the session.
Always use database-specific syntax for join conditions.
When you use Informatica join syntax, enclose the entire join statement in braces ({Informatica syntax}). When you use database syntax, enter syntax supported by the source database without braces.
When using Informatica join syntax, use table names to prefix column names. For example, if you have a column named FIRST_NAME in the REG_CUSTOMER table, enter “REG_CUSTOMER.FIRST_NAME” in the join syntax. Also, when using an alias for a table name, use the alias within the Informatica join syntax to ensure the Integration Service recognizes the alias.
The following table lists the join syntax you can enter, in different locations for different Source Qualifier transformations, when you create an outer join:
Transformation
Transformation Setting
Description
Source Qualifier Transformation
User-Defined Join
Create a join override. The Integration Service appends the join override to the WHERE or FROM clause of the default query.
Source Qualifier Transformation
SQL Query
Enter join syntax immediately after the WHERE in the default query.
Application Source Qualifier Transformation
Join Override
Create a join override. The Integration Service appends the join override to the WHERE clause of the default query.
Application Source Qualifier Transformation
Extract Override
Enter join syntax immediately after the WHERE in the default query.
You can combine left outer and right outer joins with normal joins in a single source qualifier. Use multiple normal joins and multiple left outer joins.
When you combine joins, enter them in the following order:
  1. Normal
  2. Left outer
  3. Right outer
Some databases limit you to using one right outer join.

0 COMMENTS

We’d like to hear from you!