SAP Knowledge Base Article - Preview

1531021 - A simple where clause condition is translated into a complex and slow running condition in Data Services

Symptom

  • A simple where clause in a Query transform is translated into a much more longer and complex clause.
  • The translated complex clause is inefficient and runs slower.

For example, the following where clause:

A.ID in (1,2,3)
or (A.ID=4 and B.ID in (1,2,3))
or (A.ID=5 and B.ID in (4,5,6))
or (A.ID=6 and B.ID in (7,8,9))

translates to the following:

((( "A"."ID" IN (1,2,3) or ( "A"."ID" = 4)) or ( "A"."ID" = 5)) or ( "A"."ID" = 6)) and ((( "A"."ID" IN (1,2,3) or "B"."ID" IN (1,2,3)) or ( "A"."ID" = 5)) or ( "A"."ID" = 6)) and ((( "A"."ID" IN (1,2,3) or ( "A"."ID" = 4)) or "B"."ID" IN (4,5,6)) or ( "A"."ID" = 6)) and ((( "A"."ID" IN (1,2,3) or "B"."ID" IN (1,2,3)) or "B"."ID" IN (4,5,6)) or ( "A"."ID" = 6)) and ((( "A"."ID" IN (1,2,3) or ( "A"."ID" = 4)) or ( "A"."ID" = 5)) or "B"."ID" IN (7,8,9)) and ((( "A"."ID" IN (1,2,3) or "B"."ID" IN (1,2,3)) or ( "A"."ID" = 5)) or "B"."ID" IN (7,8,9)) and ((( "A"."ID" IN (1,2,3) or ( "A"."ID" = 4)) or "B"."ID" IN (4,5,6)) or "B"."ID" IN (7,8,9)) and ((( "A"."ID" IN (1,2,3) or "B"."ID" IN (1,2,3)) or "B"."ID" IN (4,5,6)) or "B"."ID" IN (7,8,9))


Read more...

Environment

  • Data Services 12.2.2.1

Product

SAP Data Services XI 3.2

Keywords

BODI, BODS, DSXI, DI, DS , KBA , EIM-DS , Data Services , EIM-DI , Data Integrator, Composer , Product Enhancement

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.