u/mpuchala

• Enhanced dbt DAG with column-level lineage: The DAG visualization now shows columns on each model node (powered by Horizon Catalog), highlights upstream/downstream column usage on click, and adds search, depth controls, a unified side panel, and a higher model display limit of 300.
• dbt Fusion engine: A Rust-based rewrite of the dbt runtime is now supported with faster compilation for complex projects, available to all users at no extra cost.
• Multi-version dbt support: You can pin a specific dbt version (Core 1.9.4, 1.10.15, or Fusion 2.0.0-preview) per project via DBT_VERSION, override at runtime, or set an account-wide default with DEFAULT_DBT_VERSION.
• Cortex Code for dbt: Cortex Code now covers the full dbt lifecycle in Workspaces and CLI — scaffolding models, adding tests, running commands, generating docs, and inspecting deployed project files.
• Run a single dbt file in Workspaces: A run button on individual model files lets you run or build just that model without executing the entire project.
• Partial dbt project execution from the DAG: The "…" menu on a DAG node lets you run the selected model alone, its upstream parents, its downstream dependents, or all three.
• Import a dbt project object into a Workspace: You can pull the contents of an existing deployed dbt project object into a Workspace as a new folder for editing.
• SYSTEM$GET_DBT_LOG max_num_lines argument: The function now accepts an optional max_num_lines argument (default 1,000) to control how many trailing log lines are returned, capped at ~10 MB with oldest lines dropped first.

The only large EU AI provider is consolidating and entering one of the hottest and most relevant applications of this tech for Europe

I was surprised that EU cloud providers compete well on price with hyperscalers so I decided to do some deeper research and honestly the gap is surprisingly big.

Disclaimer: I'm the author of the blog post and founder of Cirran

It feels like they had a lot of momentum early last year and now it's kinda gone? We've decided to go with SQLMesh over dbt for one of our clients and it's fine, works pretty much as intended, but I expected it to be the up-and-coming challenger developing faster and putting pressure on the incumbent. Turns out dbt is actually releasing more features and pretty much covering the things that SQLMesh did better a year ago.

Not to mention LLMs still in 2026 giving me dbt solutions to SQLMesh issues and having to be clearly instructed to use official docs and Context7 to give me proper commands to run..

On the other hand `sqlmesh plan` is still a really nice feature compared to dbt CI and I don't think dbt core really has an answer yet.

If you're comparing dbt core vs SQLMesh which one do you think is worth using on greenfield projects these days?