http://www.sqlservercentral.com/blogs/vinaythakur/2012/05/22/denali-day-22-sql-server-developer-tools-ssdt-aka-juneau/

Printed 2014/08/22 01:48PM

Denali – Day 22: SQL Server Developer Tools SSDT (Aka “Juneau”)

2012/05/22

Denali – Day 22: SQL Server Developer Tools SSDT (Aka “Juneau”)

 

As stated earlier on blog on “LocalDB” discussion, developers are involved in development and has to interact with database, in this case Denali has introduced another tool called “SSDT” a visual studio shell tool for developers to work with sql server.

You have to include it in the setup to install the Sql Server Developer Tools for your installation.After installation, you have to install SSDT project Web Install, database project, you can do it from here.

Juneau is for Application developers. Who is less bother about maintenance and performance of the sql server, they are for application designer. On that SSDT is a major enhancement by Denali, using this tool developer can use the visual studio includes sql server and can play with sql server like. 

It is Packaging tool of all the sql server tools (storage ending, Analytical services, Integrated services, reporting services), so on SSDT you can work with them.

So using SSDT it makes them very easy to do this all, using a simple drag drop, you could able to generate the script, no need to remember all the commands.

It is also Cloud aware so you could easily deploy/publish the database on cloud (SQL Azure) as a target.

We could work on the offline. whenever you work on the project and create any segments, like creating any object by default it will stored in “Local” default instance on the SSDT, which we can deploy to any sql server instance later.

You can preview the changes before making the changes, just to understand what would be the impact of it.

SSDT : when you open a project/new project, it can open a “Sql server” project and you connect to server it will open a SSMS like structure on SSDT.

Query writing is so user friendly with intellisence, there is very less chances of syntax error on it.

you could compare the schema for two objects, using schema compare.

It is very user friendly

Developers would going to love it.

Ref:

http://msdn.microsoft.com/en-us/data/hh297028

http://blogs.msdn.com/b/ssdt/archive/2010/11/08/welcome.aspx

http://sqlblog.com/blogs/aaron_bertrand/archive/2011/11/21/sql-server-2012-the-data-tools-installer-is-now-available.aspx




Copyright © 2002-2014 Simple Talk Publishing. All Rights Reserved. Privacy Policy. Terms of Use. Report Abuse.