Deploy and compare a specific schema instead of a full database for Azure Synapse
- Dominant language
- C#
- Stars
- 460
- Forks
- 29
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 7
Description
**Is your feature request related to a problem? Please describe.**
With Azure SQL Synapse, multiple teams owns multiple schemas and each team wants to compare/deploy individual schema.
We have an increased need to deploy specific schema's instead of a full database, for more granular deployments. More controllable impact, less impact on the whole database.
**Describe the solution you'd like**
It would be great if there is out-of-the-box support for deploying a specific schema, instead of a full database. Hopefully as a side-effect schema compares will also speed up as only specific schema's need to be checked.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by locating the DacFx and SqlPackage schema comparison and deployment entry points for Azure Synapse, then determine how a selected schema could be specified and verify that comparison and deployment are limited to it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, sql
- Domain
- cloud, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100