Append table lost rows

Hi dgbraqe,

When not using a native SQL query, you'll need to ensure the SQL query that we generate behind the scenes includes an ORDER BY clause. This can be accomplished in a few ways.

• You can ensure that the source table you're pulling from has primary keys defined, and then include all the primary keys in your queries (ensuring they are not removed downstream, as this can actually affect the upstream SQL we send to the server). In this case, we will automatically include an ORDER BY in the SQL we send to the server.
• If this isn't possible (for example, if you're doing a Group By, or pulling from a view which can't have primary keys, etc.), it's a bit trickier. Our recommendation is that just before you do the Table.Combine, you:
  • Sort the data by a set of unique, stable keys.
  • Buffer the result of this using Table.Buffer.
  • Verify that the SQL query we generate includes the desired ORDER BY clause.

The goal is to have the data ordered consistently when it's retrieved from the SQL Server, such that the first 4,096 rows are always the same. If you need any help applying these workarounds, please let me know.

Ehren