1. René Balzano Technology Solution Professional Data Platform Microsoft Switzerland Database Development with SQL Server Data Tools (SSDT)

2. Agenda Why? How! What and when…

3. SQL Database Development is hard! SQL database development challenges: Databases are stateful entities in their very nature Dependencies make managing and preserving the state even more challenging Errors in SQL code are often found only when the code is executed Synchronizing application and database versioning adds more layers of complexity Targeting more than one version of SQL Server is very difficult to manage

4. Is there is a better way? To overcome these challenges we must work smarter Develop the database declaratively (CREATE), not imperatively (IF EXISTS (…) / ALTER ) Bring validation and verification into design time Use consistent tools when working connected or disconnected (Tools work on top of design time model) Have Schema Model differencing capabilities at our disposal (Compare and Update Models) Develop locally in a sandbox (isolated); publish changes off box (shared) Bring application and database development into the same environment and source repository 4

5. Database Development Tools 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/CLRSQL Debugging Introducing SQL Server Data Tools SQL Server Database Project

6. Foundations of SQL Server Data Tools 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 Application development integration

7. Connected Database Development DB (DEV) DB (PROD)

8. Connected/Online Development Demo

9. Connected Database Development SQL Server Object Explorer Rich T-SQL editing & debugging experience IntelliSense Buffered Declarative Editing Model-based with Error Detection Code-behind based Table Designer View/Edit/Script Data (incl. copy/paste) 9

10. Disconnected Database Development DB (DEV) DB (PROD) SSDT Project

11. Disconnected/Offline Development Demo

12. Disconnected Database Development Database definitions managed in Visual Studio Advanced language services: Go To Definition Find All References Refactoring F5 debugging with Local Database Runtime Visualize schema differences & migrate schema changes Synchronize project to database drift

13. Disconnected Database Development DB (DEV) DB (PROD) SSDT Project vNext

14. Publishing your Database Changes Demo

15. 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 Using MSBuild or new command-line tool Support for “Snapshots” Persist point-in-time representation of the schema

16. Integration between Database  Entity Data Model Automatically sync schema models Association with Database Project or Snapshot Preserve mappings and exclusions Stored Procedure sensing (parameters and output structure) Seamless F5 experience Cross-language refactoring and debugging Isolated Local Database Runtime SQL Language Services Cross-language Refactoring SQL-CLR integration* VB.NET, C# (*requires VS Pro+) Application Development Integration Database Project Application Project Entity Data Model Database Model Database Model

17. SQL Server Data Tools – Summary The standard SQL Server database development environment to: author, debug and publish complete database solutions Ships with SQL Server 2012 Hosted inside Visual Studio 2010 (Integrated shell+) Ships as part of Visual Studio vNext Pro+ Replaces the existing Visual Studio database projects Supports SQL Server 2005 and higher & SQL Azure Updated at the same cadence as SQL Azure ~Every 4-6 months Online & Offline install and update Using the Web Platform Installer Available for FREE as part of the SQL Server platform!

18. SQL Server Data Tools Resources MSDN Magazine Sept 2011 The "Juneau" Database Project The "Juneau" Database Project MSDN http://social.msdn.microsoft.com/Forums/en-US/ssdt/threadshttp://social.msdn.microsoft.com/Forums/en-US/ssdt/threads Team Blog http://blogs.msdn.com/b/ssdt/http://blogs.msdn.com/b/ssdt/ Twitter #SQLDataTools TechEd 2011 videos: Build SQL Server databases using Juneau without leaving Visual Studio Juneau Database Project integration with existing.NET applications via Entity Framework Download CTP: http://msdn.microsoft.com/en-us/data/tools.aspxhttp://msdn.microsoft.com/en-us/data/tools.aspx Look for update in Q4/2011

19. Enhancements with SQL Server 2012 SQL Server Management Studio

20. SSMS: Visual Studio Features SQL Server Management Studio is now based on Visual Studio and integrates many of Visual Studio's features: Multi Monitor Support Clipboard Ring Block Select, enhanced Zoom Task List

21. SSMS: IntelliSense Enhancements Substring matching in completion lists: Type a any part of the name of an object, IntelliSense lists all occurences

22. SSMS: Code Snippets Similar functionality to Templates, but with more flexibility Code Snippets can surround an existing block of code (e.g. WHILE ) Code Snippets are editable in XML and make use of variables (SnippetEditor on CodePlex exists for VS2010)

23. SSMS: T-SQL-Debugging T-SQL-Debugging allows for better differentiation and display of more information now Breakpoints now support additional attributes Conditional Hit Count Filter Actions Watch Expressions not only variables DataTips evaluate expressions and can be placed anywhere in the code window (i.e. close to where relevant)

24. Please help us make TechDays even better by Evaluating this Session. Thank you! Give us your feedback!

25. © 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.