Introduction to VSTS Database Professional

Introduction to VSTS Database Professional

Tejasvi KumarDeveloper Technology Specialist | Microsoft Indiatejkumar@microsoft.com

Agenda

Introduction to VSTSDatabase Development using VSTSManaging Database ChangeBuilding and Deploying a Database ProjectData GenerationDatabase Unit TestingQ & A

Visual Studio Team System

Merger of Developer and Database Editions

Customers currently owning VSTS Developer Edition or Database Edition will get VSTS Developer Edition + Database EditionVSTS Developer Edition

Unit Testing and Code CoverageStatic AnalysisCode CoverageCode ProfilingCode Metrics

Database Development Using VSTS

Database Development Life-Cycle Support Database Development Team Integration with Visual Studio Team SystemCreating Database Projects

Creating a New Database ProjectImporting Database Objects from an Existing DatabaseImporting Database Objects from a Script

Database Development Life-Cycle SupportTeam Foundation Server Process Guidance supports two new roles

Team Foundation Server Process Guidance supports two new roles

Database Administrator

Database Administrator

Database DeveloperDatabase Developer

Integrated client setup with Visual Studio Team System

Integrated client setup with Visual Studio Team System

No separate setup is required

No separate setup is required

Team Foundation Server Integration

•Version control management

•Work item tracking

•Team build integration

Database DevelopersDatabase

Administrators

Database Development Team Integration with VSTS

•Work item tracking

•Source control

•Build support

•Testing

Database work items and artifacts are managed in the same way as other team work items and work products

Database work items and artifacts are managed in the same way as other team work items and work products

Team Foundation Server

Code FilesTest FilesProject Files

DevelopmentTestingProject Management

Database ObjectsDatabase Files

Creating Database Projects

Database Project

Import database schema

Import existing .SQL script files

Create new project

SQLScript

DatabaseProject

Template

SQLServer

DatabaseDeploy

SQLScript

SQLServer

Database

Build project

Deploy project

Establish the project environment

DatabaseProject Import schema

DBA

Check in

to

Source

Contro

l

DBDev

ProductionDatabase

StagingDatabase

SCM

Trust Boundary

Isolated Iterative Development

DBA

DBDev

ProductionDatabase

Sandbox

StagingDatabase

Sandbox

Sandbox

Sandbox

SCM

• Sync• Check-out• Edit/Refactor• Test• Check-in

• Work is being drivenand tracked viawork items

Trust Boundary

Build Cycle

DBA

DBDev

ProductionDatabase

StagingDatabase

SCM

Daily Build Test

Get Latest

TestDatabase

DailyBuild

Output

Can also beused in a “Continuous”build environment

Trust Boundary

Deploy the project environment

DBA

Sync fro

m La

bel

DBDev

ProductionDatabase

StagingDatabase

SCM

SQLDeploy ScriptBuild

Deploy

Refine deploy scriptVerify

Trust Boundary

DatabaseProject

Managing Database Changes

Refactoring Database ObjectsIntroducing Database Schema VersioningSupport for Source Control Providers

Refactoring Database ObjectsDatabase Edition supports object

rename refactoringRename any SQL 2000 and SQL 2005 schema objectsVSTE DB refactoring supports changing the name of references in:

Schema objectsData generation plans ScriptsDatabase unit tests

Database Edition name refactoring supports a preview of changes before committing

Introducing Database Schema Versioning

• Schema change managed in Team System and Team Foundation Server

• Production Database is only used as the baseline for data, not for schema

• The database administrator does not have access to schema changes until it is time to deploy

• Baseline schema is under source control

•Stores versioned schema•Uses source control

•Changes can be rolled out in a scheduled, managed way

•Scripts enable administrators to manage change updates

Source Control

Database

Schema ChangesSchema Changes

ProductionDatabase

ProductionDatabase

Support for Source Control Providers

SCCI provider-basedSupport for Visual Studio based source control providers:

TFSVSS

UI support for Visual Studio through Solution ExplorerBy default, Visual Studio automatically checks out all files that are used by objectsScripts are stored as Unicode scripts by default

Building and Deploying a Database Project

Using MSBuildDeploying a Build: Full DeploymentDeploying a Build: Incremental Deployment

Data Generation

Introducing Design Time Data GenerationGenerating Data at Design TimeExecuting a Data Generation Plan

Database Unit Testing

Database Unit Testing OverviewDeveloping Database Unit TestsValidating TestsExecuting TestsCustomizing and Extending Database Unit Tests

Database Unit Testing OverviewEnsures that database changes do not break

existing codeGenerates automated tests for programmability objectsCreates a battery of tests to run with every database buildSupports design and customization of tests by using different languages:

T-SQLVB.NETC#

Builds on the existing unit-testing functionality in Test EditionIntegrates database tests with application unit tests

VSTS Database Professional

DEMO

References

Visual Studio Team System:http://msdn.microsoft.com/teamsystem

Microsoft Application Platform:http://msdn.microsoft.com/applicationplatform

Feedback / QnA

Your Feedback is Important!Please take a few moments to fill out our

online feedback form

Use the Question Manager on LiveMeeting to ask your questions now!

tejkumar@microsoft.com

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