DirectQuery limitations?

[fcerullo]

DirectQuery limitations?

Help me out understanding this guys... I thought Direct Query was great for really large Datasets, but, I am also running into a 1 million row limitation.

Specifically, I have a DirectQuery to two other pbi Datasets with similar structured tables. I am trying to create a new table with SELECTECOLUMNS

I do not want to Import these files if I can avoid it.

How can I build a new pbix using all of the dat from these 2 Datasets?

My DAX loks to be correct:

*(editted to add a comma and formatted using SQLBI)

NewTableName =
VAR existingTablename1 =
SELECTCOLUMNS (
ExistingTable1,
"NewColName", ExistingTable1[ExistingField],
"NewColumn2", ExistingTable1[ExistingField2]
)
VAR existingTablename2 =
SELECTCOLUMNS (
ExistingTable2,
"NewColName", ExistingTable2[ExistingField],
"NewColumn2", ExistingTable3[ExistingField2]
)
RETURN
UNION (
existingTablename1,
existingTablename2
)

[v-zhangti · Accepted solution]

Hi, @fcerullo 

A limit of 1 million rows can return on any query. There's a fixed limit of 1 million rows that can return in any single query to the underlying source. This limit generally has no practical implications, and visuals won't display that many points. However, the limit can occur in cases where Power BI doesn't fully optimize the queries sent, and requests some intermediate result that exceeds the limit.

Premium capacities let you exceed the one-million row limit. For more information, see max intermediate row set count.

How to configure workloads in Power BI Premium - Power BI | Microsoft Learn

Tuning query limits for DirectQuery - SQLBI

DirectQuery in Power BI - Power BI | Microsoft Learn

Best Regards,

Community Support Team _Charlotte

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.