USING DATABASE PROJECT TO MODELING SCHEMAS, INSTEAD OF DATABASES

My name is Alfonso Martín, and i work in an important spanish assurance company, in BI & DATAWAREHOUSE area. It's a pleasure share experiences and problems with you. I hope you can help me in this question, and i can help you on another occasion. Sorry for my poor english.

Actually we have more than 200 databases, with about +- 1000 schemas. Dependency between database components is very high.

We want to go to a devops strategy based in VS database projects, being the starting point of our pipeline and code saving in GIT. Our first problem is that databases are enormeous, and every developers team works to schema level, not schema databases. We have databases with more than 30 schemas, and this are managed by different developers team. My list of uncertainties:

• ¿What do you thing about working with projects that represents several schemas (one or more) instead of all database?. In this way every project will be managed by every developer team leader, without interference with other developer teams. • ¿Do you know if it's possible programmatically use schema compare for specifics schemas in a project instead all complete database?. Our tests and reviews always works with all schemas. For example. If i have a project with four schemas, and database has ten schemas, if i do a schema compare (source project, target database), the result always works with the six schemas that there are in the database, but not in my project. Is there a way to exclude programmatically this schemas?. • ¿What tools do you use to managed references and dacpac libraries?. ¿How do you inform of new libraries (dacpacs) to developers, o instead of refresh automatically database references?

Thank you in advance for all the help you can give me. I hope i can help you on another occassion.