Weird Behaviour With SQL Source Queries

[Anonymous]

Using Power Bi, any idea why SQL source query loads 3000 rows for instance in the query editor wheras it ends with 3100 rows in the final table? What explains this weird behaviour and how to overcome the problem? For the project I am handling currently, all rows needs to be loaded properly in the query editor itself as this should be followed by merging steps to other queries and grouping steps, so, not having all the rows there will ruin some of the merging step outputs and that is why having external relations will not be a solution for me, any insights on this please?

[daXtreme]

It does not matter that not all rows are loaded when you create your PQ queries. This is intentional in order not to make the editing process too slow and overwhelm the transformation engine. When you finally apply your transformations to data, ALL rows from your source will get loaded. You can, however, force the PQ editor to load all rows (if there are a lot of rows, this is not the best idea, but you can do it). Just take a close look at the interface... There's an option for this somewhere there.

[Anonymous]

Well, that is the thing, the transformation does not end correctly due to my observation?

I will try this option you are talking about, I think I know what is it.