1. MPP Engine is only applicable for Linux based deployment

2. Not all datasources are supported by the MPP Engine. Refer to Supported Data sources for a list of the datasources currently supported by the MPP Engine.

3. If a Query uses the MAX_ROWS_LIMIT option to limit the number of rows returned, then the query will not run use the MPP Engine.

4. Most of the SQL statements are supported by MPP Engine with the exception of DDLs like CREATE, DROP, ALTER and DMLs like INSERT, UPDATE, DELETE, MERGE

5. Procedure joins are not supported.

6. SQL Operators Except and Intersect are not supported.

7. The Case Sensitivity and Ignore Trailing Spaces settings may need to be altered to match with the MPP Engine’s default case sensitivity behavior. The MPP Engine uses a case sensitive approach for String columns.

8. In some cases, semi-join optimization may be chosen over a parallel plan. To force a parallel plan, the MAX_SOURCE_CARDINALITY for semi-join setting may need to be tuned.

9. For TIME and TIMESTAMP columns, the MPP Engine only handles up to 3 digits of precision for milliseconds.

10. Non-equi joins may not get scheduled for parallel processing.

11. In some cases, you may need to enable statistics for selected tables and columns in order to engage the MPP Engine.

12. Using < or > with VARCHAR may have mismatches due to case-sensitivity differences