We had numerous SQL Creators based on JDBC connections that worked in both FME Desktop and FME Server.
We are in the process of migrating our SQL Creators from JDBC to Microsoft SQL Server Non-Spatial (ADO). In doing so their SQL continues to perform well in Form, but now generates Warnings when executed on Flow.
The Warning takes the following form:
"Microsoft SQL Server Non-Spatial Reader: Getting Custom SQL schema failed. Custom SQL query 'SELECT ... WHERE ... ORDER BY ...' may execute in an unexpected manner. Make sure all columns are named (any ambiguous columns, e.g. GEOM.STBuffer(1), must have an AS clause). If there is an ORDER BY clause, either remove it or add a TOP clause."
Removing the ORDER BY does eliminate the Warnings generated on Flow.
However we enjoyed using the power of the database to presort the records prior to being transformed within the workspace.
Why is ORDER BY incompatible with Microsoft SQL Server Non-Spatial (ADO), and what other alternatives are there?