Managing the Database Lifecycle using Team Edition for Database Professionals

1. Managing theDatabase LifecycleusingTeam Edition forDatabase Professionals Randy Pagels Developer Technology Specialist Microsoft Corporation

2. Agenda What is Visual Studio Team System? Key themes of “Data Dude” Living in the “Sandbox” Database Project Types Data Generation Unit Testing Refactoring Build & Deploy Schema & Data Compare Process Guidance Setup Requirements Q&A

3. What we heard from customers“why did we build it…” • Managing Database Change is hard… • changes to the schema throughout the development process and after deployment • Managing Database State is hard… • What’s the state for the Dev, Test, or Prod environments • It’s hard to track changes to the database • Managing Database Testing is hard… • It’s hard to consistently establish the state of the database • I can’t use my live production data • Disconnect between development and database teams • Developers may make poor database design decisions • Needs to be more integrated

4. Visual Studio Team System CIO PMO Architect Tester ? Developer ProjectManager Designer Application Support Business Analyst Operations

5. Visual Studio Team System DB Pro CIO PMO Architect Tester Developer ProjectManager Designer Application Support Business Analyst Operations • Team Edition for Database Professionals • Expand to database teams • Manage Database Change • Extend Team productivity and collaboration • Integrated quality

6. Difficult to Manage Change to the schema Production Database is one version of the truth for Data and Schema DBA doesn’t have access to changes until he/she has deploy or reject choice Changes often made to production database and not rolled back into test Production Database Management Studio Schema Conceptual Overview Tuning Monitoring Schema Changes “One Version of the Truth” for Data and Schema

7. Production Database Management Studio Schema Conceptual Overview Tuning Monitoring • Schema Change now managed in VSTS and TFS • Production Database is now “One version of the truth” only for Data • DBA doesn’t have access to changes until he/she has deploy or reject choice • “One Version of the truth for Schema” is Under Source Control “One Version of the Truth” for Data • Changes can be rolled out in a scheduled, managed way • Scripts allow administrators to mange change updates “One Version of the Truth” for Schema • Offline • Under Source Control Schema Changes

8. Visual Studio Team System New! Visual Studio Team Suite SoftwareArchitects SoftwareDevelopers DatabaseProfessionals SoftwareTesters VisualStudioTeamExplorer VisualStudioIndustryPartners Application Modeling Code Analysis Performance Testing Database Projects Data/Schema Compare Performance Tuning Manual Testing Infrastructure and Deployment Modeling Data Generation Test Case Management Unit Testing Security Analysis Rename/Refactor Code Coverage Build/Deploy Unit Testing MSF Process and Guidance Class Modeling Visio and UML Modeling Visual Studio Professional Edition Load Test Agent Visual Studio Team Foundation Server Change Management Reporting Integration Services Work Item Tracking Project Site Project Management

9. Key Themes Manage Database Schema Change Enable Version Control for Database schema Mitigate Risk of those changes Leverage the “Sandbox” Establish the Database Development Lifecycle ( DDLC ) Support iterative development Incorporate the DDLC into the Software Development Lifecycle ( SDLC ) Holistic Application

10. Import database schema to populate project from existing database Changes to schema traditionally have immediate affect With off-line project nothing changes until you deploy the change Off-line Development Production Database Test Database Create table AUCTION ( id int not null, title varchar(25) not null, startDate DateTime not null, length in not null)

11. Creating a Project Represents the off-line database You are NOT connected to a live database! Simply a series of files collected together into a single logical collection The files represent the truth of your schema Connects to SCCI providers for versioning such as Team Foundation Server The database project is a first class project along with the other VS project types ( C# / VB.NET / C++, etc. )

12. The Project System & Import Database Schema Creating the “Sandbox”

13. Test Data To create a solid foundation for testing we support data generation Deterministic – always generate the same layout Matched to your schema and very customizable Extensible mechanism, build your own generators & distributions Bottom Line: Realistic values with representative distributions

14. Establish a Representative Staging Area Fill the “Sandbox”

15. Database Unit Testing Unit Testing helps ensure that changes do not break existing code Unit test designer is SQL focused Work in the language of your choice: TSQL, VB.NET, C# Builds on existing Team Test Unit Test functionality Integrate your database tests along side your application unit tests We can test the following: Generate test stubs for these types Stored Procedures, Functions, Triggers Arbitrary SQL

16. Database Unit Testing Playing in the “Sandbox”

17. Refactoring Bring power of refactoring to SQL Cascading Change Update all dependent objects in database project Schema objects, Data generation, Unit Tests, SQL Scripts Preview all changes Make an atomic change Global Undo Rename Meet corporate standards Better express semantic intent – clarity

18. Database Refactoring Leveraging the “Sandbox”

19. MSBuild Tasks • Build, deploy and data generation all implemented as MSBuildtasks • MSBuild enables: • Command line usage • Programmatic access • Chaining and composition of tasks • Team Build integration • TeamBuild on a Build Server • It is a requirement to have VSDBPro installed on the Team Build Server

20. Safely Deploying & Managing Updates “Sandbox” the Next Stage

21. Change Management Project Based Development Project Model that represents schema as objects providing a “personal sandbox” for offline development that lives within a Visual Studio Solution Team Collaborationwith Work Item and Process Integration with Team Foundation Server Automated Change Support Rename Refactoring with the ability to preview pending changes prior to execution Comparison Tools (Schema & Data Compare) allow comparisons& synchronization of schema and data with design/test/production databases Source/Version Control of all database objects with the ability to reverse engineer a database to bring it under Source Control Database Unit Testing Leverages the Test Project Infrastructure Generate “Real and Meaningful” Data Valuesthrough the ability to import information such as Row Counts and histograms from a real database Data Generator provides Repetitive Dataset Generation for tests based on saved settings Build / Deployment MSBuild Integration for Database Deployments/Builds based on Projects Either Create a new Database at the target location or Update an Existing Schema Incorporate the Database Professional into the software lifecycle and provide them with a foundation for change management and process integration.

22. Wrap Up Managed, project oriented evolution of database schema – no more rollbacks Application and database schema can now be managed together Work in “isolation”, deploying only when changes verified Leverage VSTS work item tracking and process guidance Further Questions: Randy Pagels: RPagels@microsoft.com

23. Related Content Blogs http://blog.msdn.com/gertd http://blog.msdn.com/camerons White papers What Microsoft Visual Studio 2005 Team Edition for Database Professionals Can Do for You A Security Overview of Microsoft Visual Studio 2005 Team Edition for Database Professionals Samples http://www.codeplex.com/vsdbpro MSDN Forum

24. © 2007 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.

25. MSF Process Guidance

26. MSF Integration • Extends existing MSF process guidance for database development for both: • MSF Agile • MSF CMMI • Adds 2 roles: • Database Administrator • Database Developer • Adds 3 new work streams: • Create a Database Project • Implement a Database Development Task • Deploy a Database Project • Delivered as MSF content update through the web

27. Setup Requirements • Visual Studio 2005 Team Edition for Database Professionals • Add-on to Visual Studio 2005 Team Suite • Own SKU on top of Visual Studio 2005 Professional • Need to have C# or VB.NET installed for Unit Testing • Need a local SQL Server 2005 instance for background compile time validation