May 22, 2014 at 6:54 am
Our group currently uses SSMS 2012 for database development. We have folks dedicated to database development, and a separate team who works with app changes.
Last time I tried Visual studio as a replacement for development work in SQL, it seemed a little clunky. I'm curious if anyone focused primarily on database development has recently tried using SSDT with VS 2012, 2013 and found it to be much more streamline and make a viable replacement for SSMS on the development side.
May 22, 2014 at 11:54 am
The benefit you get from using SSDT for database development is the database project itself not the environment. You get direct integration with TFS for source/version control, code analysis, and the build process so you can know if any code you've changed has errors in it before you deploy. I expect all my databases to be developed using SSDT.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
May 27, 2014 at 1:46 am
We use SSDT with Visual Studio 2013 and it works quite well; the ability to use TFS for source control is particularly useful along with generating the change scripts for use in live implementation.
I wouldn't see it as a replacement for SSMS though. It's still useful to have that around for trying things out on the development server.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply