[Feature Request]: Notify or Merge when Schema Designer is stale due to concurrent edits #21435
Description
Feature Description
When using the Schema Designer, if the schema has been changed by other users after initial load, the diagram only reflects the original state and becomes stale. If the user publishes their changes, it may result in errors due to conflicts or outdated schema. To address this, introduce a mechanism to detect if the schema is outdated because of concurrent edits. Notify the user when their view is out-of-date, and provide options to update their view, compare changes (potentially using Copilot or a diff engine), and merge to resolve conflicts. The workflow should be similar to a CI/CD flow, handling schema comparison and merges to streamline collaboration.
Problem and Motivation
Currently, collaborative edits can result in errors or lost work if changes are made by other users after a schema is loaded into the designer. This causes confusion, frustrating errors, and potentially lost data. With a notification and merge system, users would be aware of concurrent edits, able to update or merge their schemas, and reduce the risk of publishing outdated or conflicted changes.
Related Area
- Connection dialog (SQL Server | Azure browse/Fabric browse)
- Query editor
- Query results panel
- Object Explorer
- GitHub Copilot integration
- Preview/Edit data
- Table Designer
- Schema Designer
- Schema Compare
- Local SQL Server Container provisioning
- SQL database in Fabric provisioning
- DACPAC/BACPAC export/import
- SQL Database projects
- Query Plan Visualizer
- Other (please describe below)
If you selected "Other", please describe the area
No response
Confirmation
- I have searched existing feature requests and couldn't find a match
- I want to help implement this feature