3

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.

Thanks,

closed as primarily opinion-based by RDFozz, Mr.Brownstone, hot2use, McNets, mustaccio Oct 24 '17 at 14:17

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

2

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.

EXCEPT

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.