re: Responses to SSDT questions

Peter Schott — Fri, 11 Jan 2013 22:42:40 GMT

I'd probably argue that for the first question that they set those objects to "None" for build once they're in the project as well. That way they'll have the old code in version control, but can ensure that it's not being released to new servers. Any code pointing to it can also be deprecated because it won't work at all instead of partially working.

For the second person, your article at http://sqlblog.com/blogs/jamie_thomson/archive/2010/07/21/a-strategy-for-managing-security-for-different-environments-using-the-database-development-tools-in-visual-studio-2010.aspx could also be helpful. (And I've got another small tweak to the "Role" portion of the script that I'll post there shortly.) For our team, we need to test our app with certain SQL Logins at this time. Those need to be released to the local servers and then run the permissions appropriate to each environment. If that person is in a similar situation, using those post-deploy permission scripts is very helpful. Of course, having the devs be a sysadmin on their local box may be the best/easiest solution.

Totally agree that situation #2 should be automated. Use SQLPackage or MSBuild to get that going and don't forget to get the latest release code before publishing. :)