How to properly manage database deployment with SSDT and Visual Studio 2012 Database Projects?

Question

I\'m in the research phase trying to adopt 2012 Database Projects on an existing small project. I\'m a C# developer, not a DBA, so I\'m not particularly fluent with best practic

Answer 1

In my experience of using SSDT the notion of version numbers (i.e. v1, v2...vX etc...) for databases kinda goes away. This is because SSDT offers a development paradigm known as declarative database development which loosely means that you tell SSDT what state you want your schema to be in and then let SSDT take responsibility for getting it into that state by comparing against what you already have. In this paradigm the notion of deploying v4 then v5 etc.... goes away.

Your pre and post deployment scripts, as you correctly state, exist for the purposes of managing data.

Hope that helps.

JT