updating .sqlproj file (version issue with git)
We recently had a couple issues syncing from main with INFORMATION SCHEMA errors. When we reviewed the documentation Upgrade Fabric Data Warehouse System File Version in a Git Integrated Fabric workspace - Microsoft Fabric | Microsoft Learn, we noticed that we had two errors. The first is that we were self referencing in a couple PROCS, eg WH.dbo.Table from current WH. We fixed that problem, and th INFORMATION SCHEMA sync still persisted, but the self ref error went away. Then we noticed that the sqlproj file is listed as a possible cause. We have the old preview version listed in git. However, if you export the warehouse project, the actual wh sqlproj file shows up to date. So there is a difference b/w git and what is actually in the workspace. We have tried to PR the change to this file, update it directly in git, make a small change in the wh and commit directly to main to see if we could trigger the change. In the one case, we went into ADO, we updated this file directly, committed to it. It actually SHOWED as an update for a hot second, BEFORE converting to a change and the change was showing the old definition. In that referenced article, we have tried a and b, and we cannot for whatever reason get this file to update in git, which then causes sync issues. Does anyone have experience with this, a recommendation? Thanks J.
Data Warehouse deployment fails when new NOT NULL column added in schema
Greetings! We have a deployment pipeline that we are attempting to move a warehouse schema change through, we are adding some not null columns. The deployment from our Dev environment to Test is failing with the following error: Microsoft SqlClient Data Provider: Msg 24735, Level 16, State 1, Line 1 Only nullable columns can be added to an existing table. SqlMSBuild: Script execution error. The executed script: ALTER TABLE [DM_Schema].[SummaryTable] ADD [NewColumn] INT NOT NULL,CONSTRAINT [SD_SummaryTable_2d66d69a5ee8421398ab13068f0c28b4] DEFAULT 0 FOR [NewColumn] A couple of questions: 1) Why is this blocking? I can't seem to locate where NOT NULL columns are not supported by deployment pipeline? Is this a legitimate bug? 2) Why is does it appear to (rightly) add a DEFAULT 0 constraint even though no such constraint was defined in DEV environment? 3) Our current process with complicated schema changes is to use Schema Compare tool in VS Code, and promote complicated schema changes outside of the deployment pipeline, adding a column generally is not considered a complicated schema change, so just wondering if there is a way to do this within deployment pipeline? Thanks!
Varchar(MAX) in SQL Endpoint
I'm testing VARCHAR(MAX) support in a Fabric Lakehouse SQL Analytics Endpoint and discovered that it only worked after: 1. Enabling New Metadata Sync (Preview) 2. Creating a new Lakehouse after enabling the setting Existing Lakehouses didn't seem to pick up the capability. Is this officially expected, or is there a migration/upgrade path for existing SQL Analytics Endpoints?
How are teams using AI agents to automate modern data warehouse workflows?
I am exploring how AI agents can help improve data warehouse operations by automating repetitive tasks and assisting data teams with faster decision-making. Some areas I am interested in: Automating data pipeline monitoring and issue detection AI-assisted SQL generation and optimization Automatically identifying data quality issues Triggering workflows based on business events or data changes Generating documentation and insights from warehouse metadata With platforms like Microsoft Fabric Data Warehouse, how are teams approaching AI integration? Are you using: Fabric pipelines with AI-powered automation? Copilot or LLM-based assistants for warehouse development? Custom AI agents connected with data warehouse APIs? Would love to hear real-world architecture patterns and best practices from data engineers working with Fabric.
Views in Warehouse Breaks Source Control Sync
When I create a view in a warehouse and have it point to a table in a corresponding lakehouse in the same workspace, I am unable to sync a new workspace from a git branch. Reason is that the lakehouse is also new and tables/fields have not been established yet. This causes the dependency check to fail a git update. Adding a selective sync feature to Fabric will help to alleviate this problem as I would be able to do an update in two passes. Alternatively, having the ability to turn off dependency checking when updating from git would work as well. But currently, using views in warehouses that point to anything outside of that warehouse is absolutely broken from a CICD perspective. Has anyone run into this problem and found a solve for it? According to Microsoft docs, views can only point to lakehouses in the same workspace, otherwise I would have put these warehouses in a different workspace and mitigate the issue that way.Preparing Enterprise Data Warehouses for AI-Powered Applications
Hi everyone, I am exploring how organizations are preparing their enterprise data platforms for AI-powered applications. As more teams start building AI assistants and intelligent applications, having clean, structured, and accessible data becomes increasingly important. I would like to understand how the community is approaching this with Microsoft Fabric Data Warehouse. Some questions: - What data modeling approaches work best when preparing warehouse data for AI and analytics workloads? - How are teams balancing traditional BI reporting requirements with new AI use cases? - What strategies are you using for maintaining data quality and governance at scale? - Are there recommended patterns for connecting AI applications with enterprise warehouse data securely? Would love to hear practical experiences and lessons learned from teams working with Fabric Data Warehouse. Thanks!
OneLake RLS Fails Through Consumer schema Shortcut to other workspace
I’m testing a Microsoft Fabric producer/consumer architecture using OneLake Security RLS and a schema shortcut. The producer workspace contains an IT Lakehouse with three shared tables: two protected by RLS and one without RLS. The IT Lakehouse item is also shared directly with the LOB user. When the user accesses the producer Lakehouse directly from the OneLake catalog, the RLS works correctly. However, when the same tables are accessed through the LOB Lakehouse shortcut using the consumer SQL analytics endpoint, only the table without RLS works. The two RLS-protected tables fail with this error: Unable to sync the table due to insufficient permissions. Error code: TableAccessForbidden The main question is whether this is an expected limitation of OneLake Security RLS over shortcuts with the consumer SQL endpoint, or whether additional permissions or configuration are required.
Unable to Delete Warehouse
I was following along with a Lab: Explore data warehousing in Microsoft Fabric (Lab 06). I started the optional part involving a Semantic model but cancelled when I couldn't seem to select "My workspace" which is where I was working. However, I now cannot delete the warehouse within the workspace. Error: This warehouse can't be deleted because there are warehouses that were cloned from it. Select View item lineage to see them. I'm new to Fabric and so tried to use Copilot to solve the issue. Ultimately, it has suggested I post here: "From what you've described, it sounds like an orphaned transient clone reference left behind by the optional semantic model exercise, rather than a real warehouse you can delete yourself. The Fabric team or support would need to clear the metadata." My workspace contains no other items. System storage is empty. Warehouse has been emptied. sys.databases returns only master and TempWarehouse.
Switch workspace from west US to east US
Wondering how to switch WS and all contents from west US to east US. Tried backup to Git repo and restore from there - Does not work synch to a new empty workspace. Original workspace was west US, (contains pipelines, notebook, warehouse) synched WS to git repo, disconnected WS Created new WS east US tried to synch git repo to new empty WS created on east US errored out on every level and nothing got synched. It just sucks with no import export option. Any other suggestions.
