Implicit pass-through processing generates incorrect code when you use the INNER JOIN syntax. However, it will generate correct code when you use the ON clause as part of the WHERE clause and use a comma to separate the INNER JOINS.

When you run the following SQL procedure (PROC) statement using implicit pass-through to Teradata, the error shown below the example occurs:

   
select
	ic.crd_acct_nbr,
	ic.mis_dt,
	ic.blng_cyc_dt,
	ic.anr_prev_lcyamt,
	icsn.anr_prev_lcyamt as prev_prev_value
from
	rudwh.int_crd_portfolio_snapshot_c ic
	inner join rudwh.int_crd_portfolio_snapshot_c icsn
		on ic.crd_acct_nbr = icsn.crd_acct_nbr /*end of inner join*/
where
	ic.mis_dt = (select max(mis_dt) from rudwh.int_crd_portfolio_snapshot_c )
	and icsn.mis_dt = (select max(mis_dt)
		from rudwh.int_crd_portfolio_snapshot_c
		where mis_dt < ic.mis_dt
		and crd_acct_nbr = ic.crd_acct_nbr)
	and ic.anr_prev_lcyamt <> icsn.anr_prev_lcyamt;

ERROR: Teradata prepare: Syntax error: expected something between the 'select'
keyword and the 'from' keyword.

When the SQL statement is prepared to be sent to Teradata, the SQL statement generated from implicit pass-through is incorrect and results in a syntax error even though the PROC SQL code is valid and works in explicit pass-through.

Rewriting the query's FROM clause with a comma and including the ON clause at the beginning of the WHERE allows the query to be executed successfully in the database. This should achieve the same result without using the INNER JOIN statement:

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for Base SAS 9.3_M1 is available at: