One more tip regarding the build - if a schema comparison operation thinks a table exists in the database but not in the project, check the build property.
If it's set to None for an actual DDL object, then it will accidentally be ignored in the schema comparison operation.
A data warehouse contains numerous database objects such as tables, views, stored procedures, functions, and so forth.
We are very accustomed to using SSDT BI projects (formerly BIDS) for SSIS (Integration Services), SSAS (Analysis Services), and SSRS (Reporting Services).
Except for very small tables, that becomes impossible to validate that the DDL is just how you want it to be.
Therefore, I suggest using inline syntax so that your database project SQL statements are all clean and easy to read.
If you have some DML (data manipulation language) statements that are manually maintained and need to get promoted to another environment, that makes them an excellent candidate for being stored in the DB project.
In this post, I will try to convince you that using SQL Server Data Tools (SSDT) Database Projects is a really good idea.
Now let's say you are ready to promote that new column to Dev, QA, or Production. In the database project you can do a 'Schema Comparison' operation which will compare the DB objects between the project and the database.