Forum Discussion

MaxItaly's avatar
MaxItaly
Helper III
8 years ago
Solved

Best Practices with very large SQL Server Views

Hello everyone, I'd like to ask your opinion about how to handle very large SQL Server Views. We use SQL Server, and we have some views that operate on a large fact table (15+ million rows). We'd ...
Need Help
  • ImkeF's avatar
    ImkeF
    8 years ago

    Normalizing is an option worth trying. Not only because it reduces the total amount of data, but also because the tabular engine likes it more: Simply spoken: Tabular has no problem with long (narrow) table, but will tend to slow down with (even short) wide tables.

     

    So everything that will reduce the number of columns (and their cardinality) will help you here.

ImkeF's avatar
ImkeF
Community Champion
8 years ago

Normalizing is an option worth trying. Not only because it reduces the total amount of data, but also because the tabular engine likes it more: Simply spoken: Tabular has no problem with long (narrow) table, but will tend to slow down with (even short) wide tables.

 

So everything that will reduce the number of columns (and their cardinality) will help you here.

MaxItaly's avatar
MaxItaly
Helper III
8 years ago

I guess I'll try normalizing the data...

20+ columns for a fact table are way too much, and I guess it's easier than creating a cube and use it by direct query.

Thanks.