240 likes | 610 Views
DEV207. Database Development with SQL Server Developer Tools codename “Juneau”. Bill Gibson Principal PM Architect Microsoft. Mark Wilson-Thomas Program Manager Microsoft. Developing Databases is Hard!. Need to preserve data puts focus on ALTER scripts
E N D
DEV207 Database Development with SQL Server Developer Tools codename “Juneau” Bill Gibson Principal PM Architect Microsoft Mark Wilson-Thomas Program Manager Microsoft
Developing Databases is Hard! • Need to preserve data puts focus on ALTER scripts • Dependencies make even simple tasks complex • Errors detected late • Drift has to be accommodated • Hard to synchronize app and database versions • Target different editions, cloud
There is a Better Way… • Declarative not scripted • Model-based design and validation • Same tools when connected or offline • Use schema differencing for • Incremental import and deployment • Drift detection and reconciliation • Schema and app under source code control • Test locally, deploy to SQL Server or SQL Azure
SQL Server Developer Tools code-named “Juneau” SSDT Database Services Analysis Services Reporting Services Integration Services
SSDT Database Services SSDT Database Services Analysis Services Reporting Services Integration Services SQL Server Explorer Static Analysis Database Publish T-SQL Language Services Buffered Declarative Editing Table Designer Schema Compare Local Database Runtime T-SQL Debugging SQL/CLR
Demos… • Connected Development • Offline Development • Publish to SQL Azure • Drift Detection and Snapshots
Connected Development • SSMS-like explorer, query window • Buffered declarative approach • Model-based with error detection • Code-backed designer • Modern TSQL coding experience
Offline Development Working with Visual Studio Database Projects demo
Offline Development • Database definition managed in Visual Studio • Advanced language services (Go To Definition, Find All References, Refactoring…) • F5 debugging with new Local Database Runtime • Visualize and migrate schema changes
Publish to SQL Azure demo
Publish to SQL Azure • Target-aware (SQL Azure) • Publish direct, via script, or DAC • Offline and connected development for SQL Azure
Drift Detection and Snapshots • Synchronize project to database drift • Using snapshots for lifecycle management
SSDT Availability • With SQL Server “Denali” • On the web • With Visual Studio vNext
Post-“Denali” Directions • SQL Azure features supported as they emerge • Application/database development integration • On the horizon • Reference data support • Database diagrams • Query designer
There is a better way… • SSDT Database Services • Declarative, model based • Integrated tools with modern language services • Connected, and offline with local testing • Target SQL Server and SQL Azure
Resources Contact us billgib@microsoft.com mwthomas@microsoft.com • MSDN: http://msdn.microsoft.com/en-us/data/tools.aspx • Forum: http://social.msdn.microsoft.com/Forums/en-US/ssdt/threads • Team Blog: http://blogs.msdn.com/b/ssdt/ SQL Server Developer Tools Codename “Juneau”
DEV Track Resources • http://www.microsoft.com/visualstudio • http://www.microsoft.com/visualstudio/en-us/lightswitch • http://www.microsoft.com/expression/ • http://blogs.msdn.com/b/somasegar/ • http://blogs.msdn.com/b/bharry/ • http://www.microsoft.com/sqlserver/en/us/default.aspx • http://www.facebook.com/visualstudio
Resources • Connect. Share. Discuss. http://northamerica.msteched.com Learning • Sessions On-Demand & Community • Microsoft Certification & Training Resources www.microsoft.com/teched www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers http://microsoft.com/technet http://microsoft.com/msdn
© 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.