Known Issues for SQL Transformation Projects

Dots unsupported for EL project queries.

The Query Designer does not support the use of dots in schema, user, table, or column names.

Workaround: None.

Dots in table and attribute names result in invalid SQL.

The Generic SQL task component does not support table and attribute names containing dots.

Workaround: If your task references a table or attribute name containing a dot, use the Custom SQL task component.

Deletes resulting from multiple table joins may result in invalid SQL.

Invalid SQL code may be generated for a DELETE operation that uses join operations, especially if a table is joined with itself (a self-join), in which case a correlation name is required to distinguish the roles in which that table is used. If Sybase IQ InfoPrimer does not create a correlation name in the generated SQL, the DELETE operation fails.

Workaround: Before running a DELETE operation, first insert the results of the joins into a temporary table. Use the temporary table to run the DELETE operation against the target table.

Wrong query generated for joins of three or more tables and columns.

Sybase IQ InfoPrimer generates the wrong query for joins of three or more tables and multiple columns. For example, for this query:

SELECT table1.column1,
table2.column2, table3.column3
FROM (
table1 INNER JOIN table2 ON 
(table1.column1=table2.column1 AND table1.column2=table2.column2) 
INNER JOIN table3 ON 
(table2.column3=table3.column3)
)

Sybase IQ InfoPrimer instead generates:

SELECT table1.column1,
table2.column2, table3.column3
FROM (
table1 INNER JOIN table2 ON 
(table1.column1=table2.column1) 
INNER JOIN table3 ON 
(table2.column3=table3.column3) 
INNER JOIN table1 ON
(table2.column2=table1.column2)
)

Workaround: Manually correct the generated query.

Sybase IQ InfoPrimer generates invalid SQL code for an UPSERT transformation using two or more tables joined in the source query.

Workaround: Manually edit the UPSERT transformation SQL, dividing it into a DELETE operation on the target table followed by an INSERT operation.