Forum Discussion

zenisekd's avatar
zenisekd
Super User
1 year ago
Solved

Performance question

Hi,  I have a fact table, which has a couple millions of rows. Among other columns, there is "Product Code", which only contains product code and does not have any relationship to another table.  ...
Need Help
  • MattiaFratello's avatar
    MattiaFratello
    1 year ago

    Hi zenisekd, unless you are using DirectQuery, having a separate table won’t improve slicer speed.

    The performance of a slicer is mainly affected by the cardinality (the number of unique values) in the column, not the total number of rows in the fact table. 

    If there were additional attributes related to the "Product Code" (e.g., product name, category, price, etc.), then a dimension table would be beneficial for data modeling and easier filtering.

MattiaFratello's avatar
MattiaFratello
Super User
1 year ago

Hi zenisekd, unless you are using DirectQuery, having a separate table won’t improve slicer speed.

The performance of a slicer is mainly affected by the cardinality (the number of unique values) in the column, not the total number of rows in the fact table. 

If there were additional attributes related to the "Product Code" (e.g., product name, category, price, etc.), then a dimension table would be beneficial for data modeling and easier filtering.