SYMPTOM:
If users configure datamart reports when Smart Metrics are enabled, they notice that report SQL is changed such that metric calculation is performed at the SQL level against the Database Warehouse instead of the Strategy Analytical Engine level.
CAUSE:
Datamart reports do not run through the Strategy Analytical Engine since SQL should be directly running against the DB warehouse in order to create a table within it. By the same logic, users cannot make an OLAP report as a Datamart report.
When users configure a report as a Datamart report, smart metric functionality will become useless.
For example, if a report contains a compound metric, such as + , and totals are enabled, report SQL does not include this compound metric in the calculation because the Analytical Engine will calculate for it based on Smart Metrics being enabled. However, as soon as the user configures this report as a Datamart report, totals are ignored since the Datamart report does not allow totals for an Analytical Engine job. The Smart Metrics then become useless as there is no need for them in the total and as soon as Smart Metrics are unavailable, report SQL will calculate the metric as + and run it against the database warehouse.
ACTION:
Do not include Smart Metrics in datamart reports.
