SYMPTOM:
The SQL hint VLDB property places the desired custom SQL inbetween the select keyword and the columns in SQL like the following example.
Select Hint table.column columnalias,
from table
However for databases like MySQL this isn't correct syntax for table specific hints. The needed SQL for that has the following structure.
Select lutablealias.attribute
sum(ftablealias.fact)
from facttable ftablealias use key (factkey)
join lookuptable lutablealias use key (lookupkey)
group by attribute
However the needed SQL hint must be placed post table alias and can be table specific so the existing setting does not work.
CAUSE:
This is a known limitation with Strategy 9.x and 10.x.
ACTION:
Contact Strategy Technical Support for more information regarding an enhancement to support these types of SQL hints.
