Schema Filter in Source Control
Allow the of filtering of object in Source Control by schema (including the schema(s) themselves.
Database sometimes have separation of ownership based upon schema. For example, "dbo" may be owned by a .net dev team that generates all code via .Net, and changes are tracked via .Net source code, and "reporting" owned sql devs who generate code by hand. Only tracking the hand generated code (as determined by schema) via the SSMS integrated Source Control would be most appropriate.
Having a second under options where there was a Include Only/Exclude toggle and a textbox to provide a comma delimited list of schemas which are either includes or excluded, would be of benefit. Filtering should be applied to the "Refresh Database" step (only pull the meta data related to schema to be included, for example, for performance benefits in complex databases). When selecting objects in the normal commit screen, a message at the top should indicate that some schemas (and maybe information on which) are filtered out. Objects that exist in the repository should not be filtered, allowing those objects to be removed if desired.
This concept should also be extended out to deployments, to allow the same filter to only push out changes related to the selected schema.