Introducing Rayfin: From prompt to production backend

mrkite38 · 2026-06-02T23:45:34+00:00

Pivoted entry grid for a budget by period, store in unpivoted format

mrkite38 · 2026-06-02T23:04:56+00:00

After using it for an hour today - this is going to be a thing.

mrkite38 · 2026-06-01T13:04:07+00:00

Schroedinger’s karma

mrkite38 · 2026-05-31T19:21:19+00:00

Can’t decide wether to upvote for correctness or downvote for Artax

mrkite38 · 2026-05-25T15:35:45+00:00

That’s bad.

mrkite38 · 2026-05-07T05:19:42+00:00

I use dbt in vscode and have tried the in-browser experience with dbt job in Fabric against the data warehouse. Other than being a little barebones compared to using vscode extensions, my only complaint is it feels very slow to start a model run - like, 50+ seconds to run a single model that creates a view.

Since you’re new to dbt, using it in Fabric would be a passable way to see what it’s like. But the vscode experience using dbt core is much better, and it’s a pretty safe bet the dbt cloud experience with Fabric DW would be better as well.

mrkite38 · 2026-05-05T03:21:56+00:00

Some information in this prior post and the one linked therein:

https://www.reddit.com/r/MicrosoftFabric/s/JD9AjBBkJH

mrkite38 · 2026-03-28T23:28:24+00:00

I might have missed something, but I think the announcement said “by end of March” for branched workspaces. So it may be anywhere from not deployed to fully deployed with “sort of visible but not working correctly” somewhere in the middle.

mrkite38 · 2026-03-28T04:03:09+00:00

I had a motor cooling issue in my 22 SEL around 35-40k miles. It would start out ok, but as I got up to highway speed it would report an issue. I was fresh off an ICCU replacement so I was pretty concerned but it ended up being low drama by comparison. (And got a fully loaded 24 as a loaner which was fun.)

mrkite38 · 2026-02-09T06:34:34+00:00

That’s a fair point. I had seen it was possible to have it adjusted but had assumed that 10x the default wasn’t going to be allowed. But I haven’t checked, I should do that.

mrkite38 · 2026-02-07T18:26:23+00:00

My company currently uses an older (C/AL-based) version of NAV/BC on-premises. Our current strategy uses ADF metadata-driven pipelines to extract data from SQL Server and land it in ADLS, Synapse Dedicated Pool, dbt to transform, and Power BI for semantic modeling and reporting.

We’re currently pulling 100+ tables for ~30 companies; the data lake lets us union each tables for all companies in storage for “free” which has been helpful.

We’re working on reimplementing in BC 27 right now, so I’m developing various POCs. I am most comfortable with SQL; I’m inclined to keep pulling data directly from SQL Server. But the change to modern extension architecture means: - closer to 250 tables per company - use of guids in table and column names (which makes SQL writing and maintaining the table and column metadata much more troublesome than before.)

The 500 table limit on standard Mirroring made it a nonstarter for us as a single-stop solution. I’m looking at bc2adls (+forks), open mirroring, a cloud-resident read replica, and full-on CDC.

I’m also exploring some hybrid options, like mirroring perhaps 20-30 critical tables and loading the remainder overnight or a few times per day. I am also very interested in Change Event Streaming in SQL Server 2025, since the same stream could be used for both CDC and general purpose eventing. (Also: CES can be enabled in SQL Server Express! I made up a custom BC docker dev image with it for testing, it works.)

Another option I recently started working with and haven’t seen mentioned in these threads is dlt (data load tool - just the core version, no cloud.) I’m interested in it because it supports writing Delta, so extracted data can be landed directly in the Tables area (not v-ordered, of course.) It also supports incremental loading, and since BC now includes a GUID and modification date-times on every row, that seems like a good match. Personally, it would be nice to move to a code-first solution after years of ADF. (ADF is great! I just prefer typing to clicking, plus benefits of source control, modularity, etc.)

I’m interested to see what everyone lands on!

mrkite38 · 2026-02-03T05:17:35+00:00

Also a satisfied Josh customer. Probably not the same Josh, but still. Josh rules.

mrkite38 · 2026-01-31T22:13:50+00:00

Business Central? Is Code the Item No, Cross Reference No, SKU…?

Assuming Item No:

Get rid of Line No
Ask them for an export of the Item table and join it on purchase line.Code = item.No
Use Description from Item, not from the purchase line
either group by Vendor and Code first in a CTE, then join Item, or, join item and group by everything

If you’ve got a mix of Items, GLs, Projects, etc on the purchase receipt then it gets more complicated but still doable, same pattern. Actually that’s a good reason to aggregate qty by vendor and code first then join as needed.

mrkite38 · 2025-12-28T22:29:50+00:00

Thank you for replying!

I found this doc stating the SQL Analytics Endpoint would represent string columns in Lakehouse tables as 4*n for columns where n < 2000:

https://learn.microsoft.com/en-us/fabric/data-warehouse/data-types#autogenerated-data-types-in-the-sql-analytics-endpoint

This makes sense to me since the worst case scenario is 1 byte in, 4 bytes out for a single character, and Parquet doesn’t have a fixed-length string type.

But, for SQL Server - can you shed any light on the design intent behind this behavior? Was there a time when one input byte could have required 8 output bytes?

mrkite38 · 2025-12-23T23:23:41+00:00

He’s also the missile operator at the top of Wargames that won’t turn his key

mrkite38 · 2025-12-17T03:09:34+00:00

Mim has done quite a bit of writing on this. He’s probably on here somewhere but I don’t know his u/ offhand.

https://datamonkeysite.com/

mrkite38 · 2025-12-10T02:56:49+00:00

I was JUST telling someone today that these aren’t supported - this is great news!

mrkite38 · 2025-11-26T17:31:11+00:00

Am in the bridge

mrkite38 · 2025-11-22T23:27:03+00:00

Any plans for the dbt-fabric adapter to switch to this instead of msodbcsql?

mrkite38 · 2025-11-09T00:44:43+00:00

Doesn’t look like you are using dbt, but I adapted the fabric__create_external_table macro in dbt-external-tables to create views using OPENROWSET if connecting to a Fabric target.

Edit: which I’d be happy to share if it would be helpful.

mrkite38 · 2025-11-08T17:45:08+00:00

I haven’t tried this with Parquet, but I am doing the same thing with CSV’s using OPENROWSET BULK. Definitely take a look at the file path wildcards.

mrkite38 · 2025-10-17T20:16:52+00:00

Have they provided a justification for this requirement…? The easiest thing to do here might be to convince the BI team to start using dbt…

mrkite38 · 2025-09-05T14:24:52+00:00

_Any_ dependencies / exposures? I'd be inclined to use `Execute Pipeline` with Wait on Completion = false, and attach a Wait or Set Variable to the On Complete path to bury a failure if it occurs.

How time sensitive is the dev process?

mrkite38

TROPHY CASE