Deploy a specific schema instead of a full database

With the rise of Azure SQL Database (which is 1 database), we more often move from multiple databases towards 1 database with multiple schema's.

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.

We currently use https://github.com/GoEddie/DeploymentContributorFilterer in combination with version 150 to filter changes specific to a schema. It works to a certain point, unless the compare errors out before that. And unnamed constraints for example need to be named.

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.

Start by reviewing DacFx and SqlPackage's schema deployment and comparison behavior, then examine the DeploymentContributorFilterer workaround with version 150. Done means a specific schema can be deployed out of the box without requiring a full-database deployment, including cases with unnamed constraints.

Written by the indexing model from the issue text.