u/PeterDanielsCO

I'm working on some PoCs for my client related to their Databricks catalogs. I have some mirrored Databricks tables in Fabric and I have created shortcuts to them in my Fabric lakehouse. However, when I right click on the lakehouse and choose "New Semantic Model", the shortcuts to the mirrored Databricks tables do not show up in the list of tables I can add to the new semantic model. I am aware that a Databricks mirrored table is metadata only (not a "real" Fabric delta table, so I'm guessing that we would need to "materialize" (e.g. CTAS) the data in our Fabric lakehouse in order to use it for a direct lake semantic model. Anyone have experience with this?

Some MLV code in my notebook that reads from mirrorred databricks catalog tables that worked last week is no longer working. Error message:

[MLV_RUNTIME_ERROR] Unable to execute the materialized lake view. failureType: UserError errorDetails: IllegalArgumentException: Unsupported artifact type: DatabricksCatalog

Is this a recent change?

Supposedly, with the right wizardry (config, permissions, moon cycle), we should be able to see a log of Fabric Data Agent interactions in Microsoft Purview. I have found the online docs to be...challenging. Let's just say that we have yet to see this in action and would LOVE to see it in action. Can anyone help us get there? I can't even list the various config and permission changes we've made so far - apologies. It takes a village...

I wanted to fire up a new post on the new "agents app" that comes alongside vs code insiders. some initial feedback:

• The worktree and "Mark as Done" bits are confusing. Just let me work with git in the terminal. I'd like that to be my default.
• Hard to tell when I should fire up a new session vs continue one
• I've had multiple sessions, but only one shows up in the session nav
• MCP server integration is unclear and clunky.
• I like the vision. I had some positive experience, but it degraded into confusion.

What's your experience?

Has anyone worked with Fabric Data Agents and promoting them thru environment workspaces via deployment pipelines? I don't have a test environment up, so apologies for not exploring this hands-on myself. I want to understand if the agent will automatically link/bind to the appropriate semantic model data source in each workspace (dev, test, prod) as it gets promoted/deployed.

I'm using synapsesql in my Fabric spark notebook to dynamically run TSQL stored in lakehouse files against the SQL Analytics endpoint and my lakehouse. The query runs (after hacking it with "SELECT TOP 100 PERCENT", but the results are not ordered. I'm guessing synapsesql wraps my input query and the outpermost query is not ordered. Is there an option to get synapsesql to respect the ORDER BY of my query?