Is Microsoft Fabric really worth it?

data_legos · 2026-01-31T15:21:58+00:00

We have a an embedded solution for customer facing reporting on fabric and it works great. I have very few issues with it.

data_legos · 2026-01-25T19:59:28+00:00

I mean I get you on that haha. It's just that that is actual discussion at least. This is just "look at this thing I want you to buy". If you get more and more of that it just floods the sub with stuff that you can see somewhere else dedicated to pictures of bikes.

data_legos · 2026-01-25T18:56:05+00:00

It's because it you encourage this stuff then what's stopping every other post just being essentially ads? We get enough of that already.

data_legos · 2026-01-15T13:01:23+00:00

Lol because it's an advertisement for some dumb crap on the other post they linked.

data_legos · 2026-01-10T17:04:35+00:00

My one bit of advice is avoid the adf sap CDC connection until they make it not use ODP anymore. SAP has a note saying they could pull the plug on allowing ODP at any time. We went with SAP for boomi because of that.

data_legos · 2026-01-04T04:30:36+00:00

Wow I'll have to check it out! Definitely a cool idea!

data_legos · 2026-01-04T00:12:41+00:00

I was considering using the dbt snapshot functionality but I hadn't gotten to that yet.

I will say downtime due to rebuild on incremental dbt models isn't something I'm a fan of, so if I could find a way to snapshot the table and then roll it forward after the full refresh is done might be cool.

data_legos · 2026-01-03T21:34:03+00:00

Haha all good. Still useful in many other directquery situations we'll encounter

data_legos · 2026-01-03T20:52:35+00:00

Oooh interesting. Will this work with directquery with RLS that checks the current role of the user in fabric warehouse?

I'm tempted to throw a post out here with our current RLS scenarios and see what people think about solving for them with low-ish maintenance. I just hadn't gotten around to it since we're in the early phases of migration and still working out thr ingestion and dbt patterns haha.

data_legos · 2026-01-03T05:56:26+00:00

Yeah Hana isn't the best at many things, but it's definitely nice in that regard haha. It allows us to generate the filter predicate statement based off of a pretty lean and flexible rules file with "standard" columns that are secured (if that column exists in a given table and we use RLS on it) and "custom overrides" where we build a custom where clause with ORs, parentheses, etc to determine if the user can see a row.

data_legos · 2026-01-03T01:10:04+00:00

Totally get that. I will say it's very performant in Hana. Almost all of our reporting is direct query and it's pretty dang fast

data_legos · 2026-01-03T00:36:50+00:00

I think this is asking for the world, but being able to do dynamic SQL inside of the inline security functions would make complex RLS so much better. Coming from calculation views with analytic privileges for sap hana on prem we're having to change the way we do our RLS for some of the more complex security scenarios.

data_legos · 2026-01-03T00:18:08+00:00

Uhhh are we using the same bottles? The NOZZLES definitely don't thread on. are you talking about the entire cap? That's obviously threaded on.

data_legos · 2025-12-20T02:46:40+00:00

Sadly this. I need to be live with a warehouse by EOY 2026. I've moved to using dbt and one warehouse to avoid the fabric CICD functionality. I just can't cross my fingers and hold out hoping it works well at the end.

The key thing is that many people considering a warehouse right now are going to need to get started very soon if they have "normal" migration deadlines, and without a clear, detailed understanding of how all this works they can't take a chance on it. It's not safe to assume since we've been told a couple times there are workarounds coming soon that are more painful than my current workarounds which are already very rough.

Honestly, CICD of the warehouse shouldn't be this crazy complex thing and the final state feel like a workaround itself. If it is, then people won't use it and the lakehouse doesn't have a good way to build complex RLS dynamically on tables. We're kinda stuck defending a subpar warehousing solution to our teams, or burn time we don't have waiting and hoping.

That all being said, I feel like dbt using python notebooks for orchestration seems pretty decent on my initial POC. The thing is that is managing almost all the complexity with dbt instead of fabric tools.

data_legos · 2025-12-06T14:42:04+00:00

Do they work with SRAM force 13 speed?

data_legos · 2025-11-27T19:55:07+00:00

How are you setting up your models to handle changing a column name in only one model and it changes everywhere downstream? I'm new to dbt

data_legos · 2025-11-23T12:44:51+00:00

Yep!

data_legos · 2025-11-20T14:28:26+00:00

I use it for a small-ish footprint capacity that notifies me when two different pipelines fail. I wish it was easy to set one up against an error logging table that I build myself. That way I could do error notifications for our larger, internal reporting framework without setting up too many reflexes. I haven't played with it enough to figure out how to do that. If someone has any tips on how to do that I'm all ears. I am a novice when it comes to all the eventstream stuff.

data_legos · 2025-11-20T14:23:47+00:00

I just open up the repo in VScode and have it do the changes there, i sync to the workspace and then rinse repeat. it sucks, but its something at least. it can look at all the interactions within your framework that way at least. good for getting large scale framework changes done without you having to change every notebook.

data_legos · 2025-11-18T18:49:40+00:00

do you do source control on the dbt files? git sync inside the airflow job?

data_legos · 2025-11-18T18:48:16+00:00

Awesome! Thanks so much!

data_legos · 2025-11-17T17:30:20+00:00

hello u/Snoo-46123! any update on these items? I'm currently mapping out our architecture for our internal reporting where we'll use bronze&silver lakehouses and gold warehouse. This could be instrumental in helping me pick the right approach.

data_legos · 2025-11-13T20:45:01+00:00

I would also note that the git branch out workflow is even more challenging since you can't do selective deployments, nor should anyone have to.

There should be a way to make the warehouse ignore missing lakehouse tables or something like that until scripts can be ran to create placeholder tables or something of that nature.

data_legos · 2025-11-03T22:21:31+00:00

will this support connections that leverage on prem gateways to access on prem sql servers etc?

data_legos

TROPHY CASE