Model Migration & MDS Upgrade

Anand SubbarajSenior Program ManagerMaster Data ServicesMicrosoft Corporation Microsoft

SQL Server 2012®

®

Agenda

MDS Upgrade Scenarios

Model migration vs MDS upgrade

Model migration overview

Model migration – how does it work?

Model package

Demo

Model Migration vs Upgrade

Model Migration Copy the model schema or the model schema

+ data from one environment to another Both source and target systems have the same

MDS application version

MDS upgrade Move from one version to another in a specific

deployment. It involves• Installing the new bits by using SQL

Server Setup wizard• Upgrade the MDS database

schema

Model migration overview

MDS Dev

• Define the model structure and objects

• Perform initial validationMDS Test

• Perform System Integration testing

• Perform User Acceptance testing

Implementation and testing

Production

Copy the model structure and schema to the test env

Iterative process until approved by test

MDS Prod

• Upload and manage Master

Data by business users

• Requires validation and approval before updating model schema

MDS Prod

Copy the model structure and schema to the Prod env

MDS Prod (sub)

• Use the main production environment model structure & data as a starting point

• Add new entities, attributes as needed

Production – subsidiary env

Production – main env

Development env Test env

Model migration overview

MDS supports the following capabilities

• Migrate the full model structure or model structure + data

• Migrate new objects (entities, attributes, business rules etc). This is called model update

• Migrate only selected objects (Business Rules, Subscription views, derived hierarchies, entities) and their dependencies. This is called partial model deployment

Model migration – How does it work?

Source

XML file (schema only)

XML file (Schema + data)

Web UI toolMDS Web UI System Administration (System Deployment)

MDSModelDeploy.exe

On MDS installation drive:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration

Web UI tool

MDSModelDeploy.exe

Target

Web UI tool MDSModelDeploy.exe

Tools:

Usage:

Can be deployed as: Clone, Update, New

ModelPackageEditor.exe

On MDS installation drive:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration

This wizard can create and deploy packages containing only model structure

This is a command line tool to create and deploy model packages containing data or only structure.

This tool is used for editing model packages and selectively include specific objects from the model

Model Deployment – How does it work?

Source

XML file (schema only)

XML file (Schema + data)

Web UI toolMDS Web UI System Administration (System Deployment)

MDSModelDeploy.exe

On MDS installation drive:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration

Web UI toolMDSModelDeploy.ex

e

Target

Web UI tool MDSModelDeploy.exe

Tools:

Procedure:

Can be deployed as: Clone, Update, New

ModelPackageEditor.exe

On MDS installation drive:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration

ModelPackageEditor.exe

Model Deployment Package XML file saved with a “.pkg” extension Includes:

Model Structure Business Rules Version Flags Subscription views Master Data from a version of the model if included

Does not include: User defined metadata File attributes User & group permissions

MDS upgrade Scenarios SQL Server 2008 R2 to SQL Server 2012 SQL Server 2012 RC0 to RTM Migrate Database from one machine to another on

different versions

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