DATABASE SCHEMA MANAGEMENT & DEPLOYMENT USING SQL SERVER DATA TOOLS (SSDT)

Gert DrapersPrincipal Group Program Manager SQL Server Data Platform

SQL SERVER DATA TOOLS (SSDT)

• Developer-focused toolset for building SQL Server & SQL Azure databases

• Core Experiences:• Connected Development• Project Based Development• Application Lifecycle & Tools

• Fundamentals:• Declarative, model based database development• Integrated tools with modern language services • Connected and offline with local testing• Target SQL Server and SQL Azure• Detecting and managing database drift

SQL Server Object

Explorer

SQL Static Code

Analysis

Database Publishing

SQL Language Services

Buffered Declarative

Editing

Table Designer

Schema Comparison

Isolated Local

Database Runtime

SQL/CLR SQL Debugging

INTRODUCING SQL SERVER DATA TOOLS

SQL Server Data Tools

SQL SERVER DATA TOOLS

6/14/2011Microsoft Confidential

Database is a project that builds into DACPAC

Code can be tested locally (F5) Syntax and semantic validation during compilation

LocalDB

T-SQL DOM

T-SQL Compiler

Connectivity

DAC FX v3.0Visual Studio

SSDT

CONNECTED DEVELOPMENT

CONNECTED DEVELOPMENT

• SQL Server Object Explorer (SSOX)• Modeled after SSMS object explorer

• Modern T-SQL Coding Experience • Buffered Declarative Object Editing

o Model-based with Error Detection

• Imperative Script Execution• T-SQL IntelliSense

• Code-behind Table Designer• View/Edit/Script Data (incl. copy/paste)• Execute/Debug T-SQL Procedures, Functions

PROJECT-BASED DEVELOPMENT

PROJECT-BASED DEVELOPMENT

• Database definition managed in a Visual Studio project• Multi-target SQL Server {2005, 2008, 2008R2, 2012, Azure}• Advanced Language Services for T-SQL• Go To Definition/Find All References/Refactoring

• F5 debugging with LocalDB• Visualize schema differences and migrate changes• Publish direct to database or via SQL script or DACPAC• Integrated database drift detection• Point-in-time Snapshot• Drag & Drop import from SQL Server Object Explorer

APPLICATION LIFECYCLE & TOOLS

• MSBuild tasks for:• Build• Publish• T-SQL Static Code Analysis

• MSBuild in a redist (SSDTBuildUtilities.msi)• Database projects in build server environment (like Team Build)

without installing full VS on build server

• SSDT Integrates with all standard VS SCCS providers• DACFX v3• Schema Compare• Publish

K9JZ3TS

PUBLISHING & COMPARISON

PUBLISHING YOUR DATABASE CHANGES

• Target version aware:• SQL Server 2005• SQL Server 2008 & SQL Server 2008 R2• SQL Server 2012• SQL Azure

• Publish • Direct, via SQL script, or DACPAC snapshots

DAC FRAMEWORK V3.0 (DACFX)

• DAC Framework• DACFX is the core SQL redist providing modeling, reverse engineering

and deployment pipeline capabilities• v3.0 supports the full domain of SQL Server 2005, 2008/R2, 2012, and

SQL Azure

• Managed Public API• Exposes verbs for DACPAC and BACPAC operations

• Command-line tool (SqlPackage.exe)• Exposes DACPAC verbs, project publish

• DACUnpack.exe• Windows file handler for unpacking DACPAC to disk

• DACFX Clients• SSMS, SSDT, SAMP, I&E, VS Web and DB Publishing

DACPAC TRANSPORTABLE SCHEMA FORMAT

SQL SERVER DATA TOOLS – SUMMARY

• Developer-focused toolset to author, debug and publish SQL Server & SQL Azure databases

• Supports SQL Platform• Free, web updates for SQL Server and SQL Azure releases• Works in concert with other SQL Server tooling (SAMP, SSMS)

• Compatible with your development environment• Supports Visual Studio 2010 & Visual Studio 11• Migrates VS2010 database projects (*.dbproj)

MICROSOFT CONF IDENT IAL – INTERNAL ONLY

RESOURCES

• Online Setup• http://msdn.microsoft.com/data/tools Get It

• Team blog• http://blogs.msdn.com/b/ssdt/

• MSDN Forum• http://social.msdn.microsoft.com/Forums/en-US/ssdt/threads

• Articles• MSDN Magazine Sept 2011 The "Juneau" Database Project

© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.

The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after

the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.