Data360 Analyze

 View Only
  • 1.  Inner join on output to pull data from different table

    Employee
    Posted 04-13-2020 17:04

    Hi,

    I'm not an expert and need your help in selecting the correct Node to pull results.

    Please see the attached flow for visual.  

    Table A has a lot of data and it will not allow to run a select statement on ALL fields;   I'm trying to use location_ID from 2727 output and join on location_ID in table A, so in that node I only get results for same locations as listed in 2727 output (like left outer join statement however these join statements do no allow to pull data from tables, just join on already pulled data)

    Something like this:

    select * from 2727set
    left outer join Table A
    on 2727set.location_ID = TableA.location_ID

    Please note, I'm on 3.4.3 version of Data3Sixty.  

     

    Attached files

    Example.jpg

     



  • 2.  RE: Inner join on output to pull data from different table

    Employee
    Posted 04-14-2020 02:56

    The JDBC Query node allows you to create a parameterized SQL query where one or more elements can be obtained from field values in the input data. The element(s) to be parameterized are represented in the SQL query using the '?' character and the corresponding input field(s) are listed in the SqlQueryFieldBindings property e.g.

     

    Also, from Analyze v.3.5.0 the JDBC Query and JDBC Execute nodes were enhanced to support the use of dynamic SQL where the SqlQuery property could be obtained from an input field, e.g. 



  • 3.  RE: Inner join on output to pull data from different table

    Employee
    Posted 04-14-2020 05:19

    I forgot to add, the source of data for table A would be Teradata, not SQL.  



  • 4.  RE: Inner join on output to pull data from different table

    Employee
    Posted 04-14-2020 06:04

    Teradata provide a JDBC Driver:

    https://downloads.teradata.com/download/connectivity/jdbc-driver

     

    You should review the Help topic for the JDBC Query node (Note help > Input Connectors > JDBC Query). 

    In particular you will need to review the information on the placement of driver jar files cnd classpath configuration that is discussed in the 'Advanced database connection' section of the Help.

     

    The DB Query node does not support an input pin so gou cannot parameterize the query in the way possible using the JDBC Query node.