Action property of sql files in a DB project

[NowinskiK]

DevOpsBharat asked this question on my YouTube channel:

Should Action property of all the sql files in the DB project be set to Build or None when there are around 100+ developers working on the same DB project but different DB objects?

[NowinskiK]

All the files should have set "Build" if you want them to be included in the database project.
Otherwise, they won't be validated and built. The number of developers does not matter here.
If I missed something in this question - please elaborate.

[sujith0408]

Hi Kamil, This is sujith(DevOpsBharat). My actual question was that if we set the Action property to Build then the Build Time will increase which is the problem that we have. When we set the property to Build, it takes around 90mins for the build to complete.
90 mins is something that is concerning and developers cannot wait for 90mins for the entire build to complete. This is the reason why the DB automation team had excluded all the DB objects which set its Action property to None. And onlt those objects which will have change will be included as part of the sqlproject and the Action property would be set to Build.
I wanted to know what is the best way to reduce the build time when the build time is more than 90mins when we include all the DB objects and its property get set as Build.

[NowinskiK]

Out of curiosity: how many objects do you have in the solution? The biggest solution I had contained about 40 database projects and it took ~10-15 minutes to build it. Let me know whether you can share this project with me (under NDA of course), I could even talk to Microsoft Product Group about this case.