on
RE:
With SQLpackage we can't do CI/CD when change the table structure ##[error]*** An error occurred during deployment plan generation. Deployment cannot continue.##[error]Error SQL0: Deployment cannot continue because table changes that require 'ALTER TABLE' are not supported on Synapse Data Warehouse in Microsoft Fabric at this time.##[error]System.Management.Automation.RemoteException##[error]The Azure SQL DACPAC task failed. SqlPackage.exe exited with code 1.Check out how to troubleshoot failures at https://aka.ms/sqlazuredeployreadme#troubleshooting-
RE:
ShortCuts from LakeHouse to Warehouse is important, to get one copy of data. If not is possible technical this point, the I suggest to use CREATE EXTERNAL TABLE to point to the Delta Table in the LakeHouse, and the table will be only read. I think this table types in the warehouse is usually only for read and make relations between warehouse tables and Lakehouse tables. Also is necessary the work with these tables with Direct Lake.
RE:
Request is in high demand.Hop it is added to the Road map in the near future.
RE:
such a trivial request - surprised it does not exist
RE:
早く実現して欲しい
RE:
I am really missing that as well!
RE:
Hello, I have the same need and scrolled through the internet to find this idea promotion. Are there any updates about this?
RE:
We (as a client) have now run into this issue. We are unable to properly cost our BOM's due to requiring the use of non-inventory items. A 'workaround' is to create resources for each of these non-inventory lines as those costs seem be able rolled up into the cost of the BOM. While this works, its a crude way to managing inventory and costs. I would ask MS to either explain the reason why non-inventory costs are not included in the roll-up of BOM's or, fix this bug to allow proper BOM creation and management.
RE:
A must have indeed I'd say this is a bug that needs to be looked at.
RE:
The heat map is definitely needed. Please bring it back!