optimizing data load from SQL server, power query vs DAX

[y-k]

I have quite large data table I would like to load on beginning as source data table.
Then I like to filter out data, into smaller tables.

I just realized, by using duplicate or reference on source data table, I create a new SQL query. which is fine in a sense, but I have +100 smaller tables I wish to create, that means +100 seperate SQL querries, that is too much for me.

Is there any other way to do this is power query, or should I use DAX?

Only reason I like to use power query is, that I can easily create index number for my small tables, is there way to do this in DAX?

[Sahir_Maharaj · Accepted solution]

Hello @y-k,

If you prefer to use DAX, you can use the "FILTER" function to create new tables that contain only the rows you want. To create index numbers, you can use the "RANKX" function.

Small Table 1 = FILTER('Large Table', 'Large Table'[Column 1] = "Value 1" && 'Large Table'[Column 2] = "Value 2")

Small Table 1 with Index = ADDCOLUMNS('Small Table 1', "Index", RANKX('Small Table 1', 'Small Table 1'[Column to Rank],,ASC))

Let me know if this works for you.

[y-k]

@Sahir_Maharajthank you!
What about Power query solution, does such exist, or does it require always reloading each +50 querries, or is there way to reuse one query, and split it into smaller tables without reloading +50 different querries?


And about DAX solution, do i need to create this measure for each of my +50 tables, or is there way to do it in mass?