The use case I am working on is a composite database project inheriting from a core database project and which just contains objects for a single schema owned by a single team.
The idea being that the team project can only make changes to objects explicitly owned by the team.
Passing a filter as below
SqlPackageFilter=IgnoreSchema!(\bMySchema\b)
... works for schema scoped objects and removes changes for other schemas but I still see script generated for non schema scoped objects such as CLR assemblies, file groups, partition schemes.
The use case I am working on is a composite database project inheriting from a core database project and which just contains objects for a single schema owned by a single team.
The idea being that the team project can only make changes to objects explicitly owned by the team.
Passing a filter as below
SqlPackageFilter=IgnoreSchema!(\bMySchema\b)
... works for schema scoped objects and removes changes for other schemas but I still see script generated for non schema scoped objects such as CLR assemblies, file groups, partition schemes.
Do you think these semantics need changing?