Columns added to Delta table are not propagated to the serverless SQL Pool

[mstetka-fr]

The section "Change Maintenance" implies that any schema related change to a shared metadata object will automatically be synchronized to the Serverless SQL pool.

This is not the case when adding a column to an existing DELTA table.

The only workaround I've identified is to rename the table and then rename it back to the original name.

%%sql 
--Create a DELTA table and then wait for it to appear in the lake database catalog
CREATE TABLE change_sync_demo (Id int)  
USING DELTA;

After running the above and seeing the table exist in the Lake database, run the following:

%%sql
ALTER TABLE change_sync_demo ADD COLUMN (Value2 int);

This Value2 column will not be synchronized until something else triggers the synchronization.

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 94b77aa3-658b-2243-9e41-f9a1cad93d82
• Version Independent ID: 7f3477b3-cb83-92e1-74a8-11c7570ced1a
• Content: Shared metadata model - Azure Synapse Analytics
• Content Source: articles/synapse-analytics/metadata/overview.md
• Service: synapse-analytics
• Sub-service: metadata
• GitHub Login: @juluczni
• Microsoft Alias: juluczni

[Naveenommi-MSFT]

@mstetka-fr Thanks for your feedback! We will investigate and update as appropriate.

[RamanathanChinnappan-MSFT]

@mstetka-fr

I've delegated this to @juluczni , a content author, to review and share their valuable insights.

[bandersmsft]

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close