Fabric Semantic Models vs Analysis Services Tabular Model

I'm building out my first Fabric data warehouse, my previous experience was an on prem sql server data warehouse that pushed out to a tabular model in Visual Studio then deployed to Analysis Services. I have my fact and dimension tables in Fabric and created views off those table to shape the data for use in a semantic model. However, I got a warning that using views wasn't ideal and should use tables. My question, is there a similar feature in Fabric to Visual Studio's tabular model or do I need to create a series of tables within the data warehouse that will be used in the semantic model?

If I need to create another level of tables that will feed the semantic model, is there a function to partition that data built into Fabric or will I have to design that process leveraging stored procedures incrementally refresh the semantic model tables?

2 comments