Академический Документы
Профессиональный Документы
Культура Документы
In this example you can see we have a physical table in the database, W_CUSTOMER_D, and
that I have created an Alias ojbect based on that table of Dim_W_CUSTOMER_D. In the ID
column the two objects have IDs of 3001:111 and 3001:222 respectively. If we were using the
table in our query, we can deduce we will use an alias of T111. Actually we used the Alias object
and the database alias generated would be T222. You can see it is the latter segment of the ID
that is used.
We can now add the hint; a hint can not be added to an OBIEE Alias object, only to an
underlying Table object. We open the properties for the table object and add the hint to the text
box as below.
You can see that the hint is applied to the OBIEE Alias object, T222; but we are creating
that definition on the underlying Table object. If there were no Alias object and the table itself
were used in the query then we would need to use the SQL generated alias of T111.
Hinting an Alias Object
But what do we do if we have multiple Alias objects sharing the same underlying Table object;
this happens all the time.
We cant apply the hint to the Alias object itself; instead we apply it to physical joins to and
from the Alias object. The screenshot below shows where we apply the hint for the Alias table
above.
You can see that weve populated the hint textbox referencing the SQL alias T222. Whenever
this join is used the hint will be added to the query.