When creating a TFS Visual Studio 2017 solution with SQL Server 2016, should the solution contain

  1. one database project per solution, or

  2. multiple database projects in a single solution?

Our system has databases which are interlinked/cooperate in creating one service. I believe the correct answer is "multiple databases in one TFS Visual Studio solution"; please validate.



A solution is meant to cover multiple like projects together. So for example, I have a "Data Warehouse Solution" that has all of my SSDTs related to our data warehouse. I then have a different solution for my "RDBMS Project," with more projects inside of that. It is a logic grouping for user ease.

There is nothing stopping you from having one master solution with tons of projects, or one project per solution.


I found the need to have an SSDT for the database server itself, if you are keeping track of server objects created at the server level. For example, security objects. Then I found that you couldn't create a reference to the database server. You had to create a SSDT project just for it.

| improve this answer | |