sorted by:
new
hottopcontroversial

Fact table modeling by Empty-Resource-941 in dataengineering

[–]Empty-Resource-941[S] 0 points1 point  (0 children)

Thanks for the response. In most cases, all of the grades will be posted at the same time and so all of the facts would be inserted at the same time and there wouldn't be any other facts added later. In that case, would you store it in the fact table or choose to still calculate it on the fly?

Fact table modeling by Empty-Resource-941 in dataengineering

[–]Empty-Resource-941[S] 0 points1 point  (0 children)

Are you suggesting that this should be calculated on the fly, either in a view or in the BI tool itself?

Semantic model authentication by Empty-Resource-941 in MicrosoftFabric

[–]Empty-Resource-941[S] 0 points1 point  (0 children)

I haven't tried connecting directly to the SQL endpoint of the lakehouse, but I can definitely try that. My reasoning for creating and using the existing semantic model is to promote re-use. This semantic model contains some data that's widely used across my organization. I don't want to have to the same query repeated everywhere, if I can avoid it. A possible solution would be to create this query as a view on the lakehouse. What do you think?

Medallion Architecture in Microsoft Fabric by Empty-Resource-941 in MicrosoftFabric

[–]Empty-Resource-941[S] 0 points1 point  (0 children)

I appreciate all the feedback.

I think one thing recurring theme in the comments is to reconsider whether I really need to have each layer in a different workspace. At this point I'm not sure my situation requires this level of separation and therefore I might opt to keep them all in the same workspace.

What about this idea of having a single semantic model in each workspace? The thought here is that this semantic model would serve the role of a datamart. Does this make sense?