It would be nice if Source Control can split a database to multiple fragments (based on filters - for example per schema) and setup a repository folder for each fragment.
The use case: we have many projects which are using always the same core tables and functions (for example notification, settings, user management, ...) and the others are custom specific in custom owned repositories. I want to simplify change tracking and version handling of these core elements and share them in a public repository so each customer can use them. Currently we are updating a core procedure and copy this into each customer repository and this is annoying.
In another project we have a single application with many modules (common and customer specific modules) and not each customer is using each module. With this feature we could bind only the used modules to each customer database.