Transcript Model Migration & Application Upgrade - TechNet Gallery
Agenda
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
Implementation and testing
Iterative process until approved by test
MDS Dev • • Define the model structure and objects Perform initial validation MDS Test • • Perform System Integration testing Perform User Acceptance testing
Copy the model structure and schema to the test env
Production • MDS Prod (sub) • Use the main production environment model structure & data as a starting point Add new entities, attributes as needed
Copy the model structure and schema to the Prod env
MDS Prod • • Upload and manage Master Data by business users Requires validation and approval before updating model schema
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?
ModelPackageEditor.exe drive:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration drive:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration packages create and deploy model containing data or only structure. Source Target Can be deployed as:
Clone, Update, New
Model Deployment – How does it work?
drive:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration drive:\Program Files\Microsoft SQL Server\110\Master Data Services\Configuration Source Target Can be deployed as:
Clone, Update, New
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