SQL Server 2012 (“Denali”): SQL Server Data Tools (SSDT), codename ‘Juneau”

SQL Server Data Tools (SSDT), codename “Juneau”, is the name for the new SQL Server Development Tool to be released along with the next version of SQL Server 2012, codenamed “Denali“.  Its purpose is to provide a single development environment for all database-related project types by bringing BIDS (Business Intelligence Development Studio), “Data Dude” tools in Visual Studio 2010 Premium and Ultimate editions, and SSMS (SQL Server Management Studio) into the same IDE.  It is based on the Microsoft Visual Studio 2010 shell.  It is not available in the current CTP1 of Denali, but it will be shipped with the next CTP release (UPDATE: CTP3 made available here on July 12th, 2011, and download Juneau here).

UPDATE 10/13/2011: The official name is SQL Server Data Tools (SSDT).  And BIDS will no longer be a seperate product.  Download CTP4 of SSDT here.

UPDATE 9/17/2012: You can download the latest production version of SSDT for both Visual Studio 2010 and Visual Studio 2012 at Get Started with Microsoft SQL Server Data Tools.

SQL Server Data Tools (SSDT) provides functionalities for both data-tier and app-tier developers to perform all their development work against any SQL Server platform within Visual Studio.

Not so much a replacement for SSMS (which is focused on SQL Server management), but a home for when you need to do database development.  The goal is to take the tasks and features that are routinely used by developers in SSMS and bring them over into SSDT.  This means you can avoid the Alt + Tab scenarios that kept you leaping between BIDS and SSMS in previous versions of SQL Server.

Database development tools already available in VS2010 will be converted to “Juneau”.  All functionalities currently available will remain so or will be enhanced.  You can think of it as a replacement for BIDS that uses project types of Database Services (a new service which is essentially the “Data Dude” tools in Visual Studio 2010 Premium and Ultimate editions), Analysis Services, Reporting Services, and Integration Services.

Some notable new features:

  • The Server Explorer in Juneau now provides you with an SSMS-like view of your database objects
  • The ability to analyze a set of changes and generate a script that will then update the database based on those changes in the development environment
  • Preview database updates – The commit operation will provide a deployment report, which contains a preview of all the actions it is going to take, together with potential issues it has identified
  • Improved intellisense
  • Ships with a single-user lightweight SQL Server version to help with debugging
  • Refactor table names, field names, etc, without losing data
  • Debug stored procedures
  • Can target different versions of SQL Server, including Azure
  • Can take a snapshot of the project.  Allows you to have versions of your database.  Can track history of changes over time
  • Can compare your project to the current state of the database.  So you can see, for example, indexes added to the live database and add those index changes to your project.  Can do things like a schema compare between two versions: a developer can start with a snapshot, make changes, then send the differences to the dba to implement;  ISV’s can track databases it has sent to customers and send them scripts to update their database
  • On the horizon: reference data support (storing data with the schema), database diagrams, query designer
  • Any errors caused by editing in either the TSQL Editor or Table Designer immediately show up in the Error List pane, and are platform specific
  • You can now add SQLCLR objects directly to the same database project that is opened, without resorting to opening a specific SQLCLR project.  Your TSQL stored procedures can interact with your SQLCLR objects within the same project.  Debugging and deployment can also happen seamlessly
  • Coding support that includes: Go To Definition and Find All References; the Refactor contextual menu which enables you to rename or move an object and do a preview of all affected areas before committing to the change
  • You can create an ADO.NET Entity Data Model and choose to have the model contents generated from an existing database project.  Fine-grained synchronization control settings are provided to enable you to specify how changes are propagated between the entity data model and the database project

More info:

Video: Introducing Microsoft SQL Server Developer Tools,Code-Named “Juneau”: An Introduction to Doing Database Development in a Modern Way from TechEd 2011

Video: Microsoft SQL Server Developer Tools,Code-Named “Juneau” and the ADO.NET Entity Framework: Best Friends Forever from TechEd 2011

Official Microsoft Blog: SSDT Team Blog

Review by Robert Sheldon: Finally, development across platforms in Microsoft Visual Studio 2010

The ‘Juneau’ Database Project

Top VSDB->SSDT Project Conversion Issues

SQL Server Data Tools CTP4 vs. VS2010 Database Projects

What is SQL Server Data Tools (SSDT)?

SQL Server 2012–SQL Server Data Tools

FAQ: Microsoft SQL Server Data Tools

SQL Server Data Tools: A Work in Progress

Get to Know SQL Server 2012’s SQL Server Data Tools

About James Serra

James is a big data and data warehousing solution architect at Microsoft. Previously he was an independent consultant working as a Data Warehouse/Business Intelligence architect and developer. He is a prior SQL Server MVP with over 25 years of IT experience.
This entry was posted in SQL Server, SQL Server 2012, SQLServerPedia Syndication, SSDT/Juneau, Visual Studio 2010. Bookmark the permalink.

22 Responses to SQL Server 2012 (“Denali”): SQL Server Data Tools (SSDT), codename ‘Juneau”

  1. Pingback: SQL Server “Denali” | James Serra's Blog

  2. Pingback: Log Buffer #227, A Carnival of the Vanities for DBAs | The Pythian Blog

  3. Pingback: Pythian Group: Log Buffer #227, A Carnival of the Vanities for DBAs | Weez.com

  4. Pingback: SQL Server "Denali": CTP3 now available! | James Serra's Blog

  5. Pingback: SQL Server “Denali”: CTP3 now available! - James Serra's Blog - SQLServerCentral.com

  6. Pingback: SQL Server 2012 and other PASS annoucements | James Serra's Blog

  7. Pingback: SQL Server “Denali”: Installing on a Virtual Machine | James Serra's Blog

  8. Pingback: SQL Server 2012 RC0 is here! | James Serra's Blog

  9. Pingback: A Developer Overview of SQL Denali 2012 - dBforums

  10. Kris Hokanson says:

    Very informative and well written post but I noticed that you refer to SSDT as both SQL Server Data Tools and SQL Server Developer Tools (see third paragraph). Could that be a reference to an older technology or just a casualty of today’s world of TMA (Too Many Acronyms)?

    • James Serra says:

      Hi Kris,

      Glad you like the post. I have corrected that acronym…good catch. SQL Server Developer Tools was what it was called very early on, then they changed it to SQL Server Data Tools. But definitely TMA!

  11. Pingback: SSDT - Installation confusion | James Serra's Blog

  12. Pingback: Visual Studio 2012 does not support BI | James Serra's Blog

  13. Pingback: SQL Server Data Tools (SSDT) - September 2012 update | James Serra's Blog

  14. Pingback: Get Started with Microsoft SQL Server Data Tools « Hansa-Cequity's Knowledge Centre

  15. Pingback: SQL Server 2012: New Business Intelligence features | James Serra's Blog

  16. Walt says:

    I recently had to format my development box. Prior to the disaster, I had VS2010 pulling up a solution with a .rptproj Project as a part of it. I could edit the reports and all was well. Now I can’t recall how I got my VS2010 installation to that point. I’m getting the “.. .rptproj is not supported by this version of the application” error and that part of the solution doesnt open. Hoping someone can help me.

  17. Pingback: Can I use SSDT for the 2008 BI stack? | James Serra's Blog

  18. Pingback: SQL Server Data Tools (SSDT) – December 2012 update | James Serra's Blog

  19. Pingback: Managing Schemas And Source Control For Databases | James Serra's Blog

  20. Pingback: SQL Server Data Tools (SSDT) – June 2013 update - SQL Server - SQL Server - Toad World

  21. Pingback: SQL Server Data Tools (SSDT) – August 2013 update - SQL Server - SQL Server - Toad World