1. Entity Based Staging SQL Server 2012 Tyler Graham
Senior Program Manager
Master Data Services
Microsoft Corporation
Microsoft
SQL Server 2012

2. Agenda Staging Overview New Benefits of EBS Staging Tables structure
Import Types and Batch Tags
Error Management
Demo

3. Staging Overview SQL Server 2008 R2 Staging Framework
3 Tables – tblStgMember, tblStgMemberAttribute, tblStgRelationship
Data was loaded as name-value pairs
SQL Server 2012 – Entity Based Staging
Staging Table is created per Entity
Hierarchy enabled entities will have 2 additional tables – Consolidated Members and Relationships

4. Benefits of Entity Based Staging
More intuitive interface
Ability to secure staging at the entity level
Significant Performance improvements
Easy integration with SQL Server Integration Services

5. Staging Table Structure
Generic Architecture, Support any Possible Data Model
Can be managed in Batches
Three Staging tables created automatically when entities are created
Names are customizable
Table
Description
stg.<Entity>_Leaf
Create, update, and delete leaf members and their attributes.
stg.<Entity>_Consolidated
Create, update, and delete consolidated members and their attributes.
stg.<Entity>_Relationship
Move members in an explicit hierarchy.

6. Import Types Import ID Name Description 0 or blank Merge Optimistic
All populated record information will loaded into the Entity when either the member does not exist or the member exists. Nulls will be ignored. 1
Insert
Only new member records and their attributes will be loaded into the MDS entity all existing records will be flagged as member code already exists. No attributes on pre-existing records will be updated. 2
Merge Overwrite
All populated record information will loaded into the Entity when either the member does not exist or the member exists any blank element in the EBS table will overwrite values within the MDS entity. 3
Delete
Only the member code will be evaluated and these records will be soft deleted from the MDS entity 4
Purge
Only the member code will be evaluated and these records will be removed from the MDS entity version that these records are staged into. 5
Delete Override
Only the member code will be evaluated and these records will be soft deleted from the MDS entity. This will set any Domain Based Attribute references to Null to complete the operation. 6
Purge Override
Only the member code will be evaluated and these records will be removed from the MDS entity version that these records are staged into. This will set any Domain Based Attribute references to Null to complete the operation.

7. Batch Tags
50 character tag to allow multiple simultaneous loads through entity staging.
Trigger stored procedure with the provided batch tag.
System batch Id will be assigned in the import process.

8. Error Management In SQL Server 2008 R2 1 error per row
In SQL 2012 all errors are now logged
Error views can be reviewed to correct issues.
Stg.viw_<entity staging name>_MemberErrorDetails

9. 10/13/ :38 AM
© 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.
© 2010 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.