question

It's actually getting kind of old, but I wrote several chapters for a book called [SQL Server Team Based Database Development][1] (free to download at the link). It covers quite a lot about setting up different environments, why you might need one of a certain type or another, etc. The tool examples, both Microsoft and Red Gate are VERY out of date, so it's not that useful in that regard. But the rest of the discussion is still applicable. I also [have a presentation][2] where I talk a lot about deployment best practices. Since development leads directly to deployment, many of the things there are probably applicable to what you're setting up. This is the tool free version of the presentation. If you want to also see the Red Gate tools in use, [we have a second presentation][3]. Personally, I'd strongly recommend you let the developers have sandbox environments. Whether that's just running stuff locally on their laptops, a designated VM on a laptop, or a VM or instance that you control, let them all break things to their hearts content, as fast as they can, without hurting others. Then, set up an integration environment where you bring their code back together for testing prior to sending it to QA/Test. I'd also suggest a continuous integration environment where you test all the code as it goes into source control. Oh, yeah, and source control the database code, just like the app code. [1]: https://www.simple-talk.com/books/sql-books/the-red-gate-guide-to-sql-server-team-based-development/ [2]: http://thefutureofdeployment.com/recording-of-grant-fritcheys-database-deployment-best-practices-webinar/ [3]: http://thefutureofdeployment.com/webinar-recording-how-to-automate-your-database-deployment-process-using-red-gate-deployment-manager/