Your SlideShare is downloading. ×
0
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Sql server 2012_sp1_11_of_12_credible_consistent_data_level300_dark_deck

230

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
230
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. CREDIBLE, CONSISTENT DATABreakthrough Insight
  • 2. THE FANTASTIC 12 OF 2012 1 2 3 4 5 6 7 8 9 10 11 12
  • 3. CREDIBLE, CONSISTENT DATACREDIBLE, CONSISTENT DATA FOR TRUSTED CRITICAL DECISION MAKING • • • • • • • • • • • • • • • •
  • 4. BI SEMANTIC MODEL
  • 5. BI SEMANTIC MODEL—BENEFITS
  • 6. BISM KEY FEATURES
  • 7. BISM HIGHLIGHTS
  • 8. BI SEMANTIC MODELFlexibility
  • 9. BI SEMANTIC MODELRichness
  • 10. BI SEMANTIC MODELScalability
  • 11. BI SEMANTIC MODEL—ARCHITECTURE
  • 12. BI SEMANTIC MODEL
  • 13. XVELOCITY IN-MEMORY ANALYTICS ENGINEDesign Principles
  • 14. XVELOCITY IN-MEMORY ANALYTICS ENGINEStorage
  • 15. BISM SUMMARYSingle model for users, multiple ways of building solutions
  • 16. ENCODING
  • 17. ENCODING EXAMPLE
  • 18. ENCODING EXAMPLE CONT.Delivery Type column: hash encoding
  • 19. ENCODING EXAMPLE CONT.Product column: hash encoding
  • 20. ENCODING EXAMPLE CONT.Sales Amount column: value encoding
  • 21. ENCODING EXAMPLE CONT.All columns encoded
  • 22. ENCODING SELECTION
  • 23. COMPRESSION
  • 24. RUN LENGTH ENCODING (RLE)
  • 25. RUN LENGTH ENCODING (RLE) CONT.
  • 26. BITWISE COMPRESSION
  • 27. CONTROLLING SEGMENT SIZE AND COMPRESSION0 (default): 8M for Analysis Services, 1M for PowerPivotValue must be power of 2, should be at least 1MLarger => generally better compression, faster queries with lower overheadSmaller => smaller working set during processing-1 (default): 10 secSmaller => greedy algorithm gives most gains in the beginningLarger => almost always better compression, higher query performanceIncrease for large number of columns (~>200)
  • 28. COMPRESSION RESULTS* ON REAL WORLD DATA*Based on data from early adopter customers
  • 29. PROCESSING OPTIONS
  • 30. INCREMENTAL PROCESSING
  • 31. ADVANCED PROCESSING
  • 32. SERVER MEMORY MAP
  • 33. BI SEMANTIC MODEL—SCENARIOSPower view over a sales model
  • 34. BI SEMANTIC MODEL—SCENARIOSExcel over a Sales model
  • 35. BI SEMANTIC MODEL—SCENARIOSExcel over a Finance model
  • 36. BI SEMANTIC MODEL—SCENARIOSPower View over a Finance model
  • 37. DATA MODEL
  • 38. BEST PRACTICES FOR TABULAR MODELS
  • 39. OPTIONS FOR WORKING WITH LARGE DATASETS
  • 40. BI SEMANTIC MODELWhat About Existing Analysis Services Applications?
  • 41. BISM & UDM COEXISTENCE
  • 42. HOW SHOULD I BUILD MY MODEL?
  • 43. BUSINESS LOGIC
  • 44. DAX – DATA ANALYSIS EXPRESSIONSNavigate relationshipsDynamic calculation of measuresTable valued functionsTime Intelligence
  • 45. DAX ENHANCEMENTS IN SQL SERVER 2012
  • 46. DAX FOR THE BI PROUSERNAME() / CUSTOMDATA() functions in DAX
  • 47. QUERYING THE BI SEMANTIC MODEL WITH DAX
  • 48. DAX QUERY SYNTAXDEFINEMEASURE Table1 [measure1] = <DAX_Expression>EVALUATE<DAX Table Expression>ORDER BY <DAX_Expression> [ASC | DESC]
  • 49. DATA ACCESS AND STORAGE
  • 50. DESIGN TOOLS
  • 51. WHAT’S NEW IN INTEGRATION SERVICES
  • 52. UPGRADING FROM PREVIOUS VERSIONSProject Deployment Model is optional“Legacy Deployment Model” -> “Package Deployment Model”Everything continues to workExcept DTS, and ActiveX Script TaskDTS packages should be migrated to 2008 then upgradedCustom components need to be recompiledNo code changes required (unlike 2005 -> 2008)Connection strings - SQLNCLI10.1  SQLNCLI11.1Scripts should automatically upgrade
  • 53. SQL SERVER CDCEnable it on the source system -- enable CDC on the database exec sys.sp_cdc_enable_dbAutomatic capture of changesConfiguration options -- enable CDC on a table exec sys.sp_cdc_enable_tableUses transactional replication @source_schema = Ndbo, @source_name = NMyTable,SQL Server 2008 and later @role_name = Ncdc_admin, @supports_net_changes = 1
  • 54. CHANGE DATA CAPTURE - HOW IT WORKSEnable it on the Source DatabaseInserts, Updates, and Deletes are automatically trackedConsume the changes
  • 55. CDC COMPONENTS FOR SSIS 2012
  • 56. WORKFLOW
  • 57. INITIAL LOADScenario 1: Active databaseMark Initial Load StartBulk load from source to destinationMark Initial Load EndScenario 2: Inactive database or using snapshot/flashbackMark CDC start Oracle – provide the System Change Number (SCN) SQL – provide the Log Sequence Number (LSN) or snapshot name CDC Control Task will use current value if none is providedBulk load data from source to destination
  • 58. INCREMENTAL LOADUse CDC Control Task to get the processing rangeRead from cdc_states tableStored in package variableUse CDC Source to read changes since last runProcess change rowsUse CDC Control Task to mark processing end
  • 59. USING THE REPROCESSING INDICATOROption in the CDC Source to include a reprocessing flagAdds __$reprocessing column to data flowFlag is set to True for rows that require special handlingRows that overlap with initial loadReprocessing a range after a failure
  • 60. BOOKS ONLINE RESOURCESCDC Flow Componentshttp://msdn.microsoft.com/en-us/library/hh231087.aspxTuning the Performance of Change Data Capturehttp://msdn.microsoft.com/en-us/library/dd266396.aspxComparing Change Data Capture and Change Trackinghttp://msdn.microsoft.com/en-us/library/cc280519.aspx
  • 61. PROCESSING MODESAllAll with Old ValuesNetNet with Update MaskNet with Merge
  • 62. WHICH PROCESSING MODE SHOULD I USE?All vs. NetAll changes Do I need to record every change? Do I enjoy complicated ETL work?Net changes Do I want to push the work to the source system?Update Mask / Old Values Do I need to do something when specific columns change?
  • 63. PROCESSING MODE - ALL
  • 64. PROCESSING MODE - ALL
  • 65. PROCESSING MODE – ALL WITH OLD VALUES
  • 66. PROCESSING MODE – ALL WITH OLD VALUES fx
  • 67. PROCESSING MODE – NET
  • 68. PROCESSING MODE – NET
  • 69. PROCESSING MODE – NET WITH UPDATE MASK
  • 70. PROCESSING MODE – NET WITH UPDATE MASK
  • 71. PROCESSING MODE – NET WITH MERGE
  • 72. PROCESSING MODE – NET WITH MERGE
  • 73. CDC FOR ORACLE
  • 74. SETUPOracle CDC components are not installed by defaultMSIs found on SQL media under: ToolsAttunityCDCOracleOracle CDC ServiceAttunityOracleCdcService.msiOracle CDC DesignerAttunityOracleCdcDesigner.msi
  • 75. ORACLE CDC SERVICE CONFIGURATIONName your serviceProvide a service accountSQL instance informationCDC master passwordOne service per Oracle DB
  • 76. ORACLE CDC DESIGNERAllows you to create and manage Oracle CDC InstancesYou can have multiple instances per CDC ServiceAn instance containsOracle database connection informationTables and columns being trackedMirroring SQL Server instance information
  • 77. ORACLE CDC DESIGNER – CREATING AN INSTANCE
  • 78. ORACLE CDC DESIGNER – MANAGING AN INSTANCEList all of your servicesand CDC captureinstancesControl the instancestate (start, stop, reset)Regenerate setup scripts
  • 79. SUPPORTED VERSIONSSQL Server (Enterprise Edition)2008, 2008 R2 and 2012Oracle10g Release 2 10.2.0.1—10.2.0.5 (patch set as of April 2010)11g Release 1 11.1.0.6—11.1.0.7 (patch set as of September 2008)11g Release 2 11.2.0.1—11.2.0.2 (patch set as of November 2010)
  • 80. COMMON QUESTIONSDo I need any special permissions?Getting current LSN during initial load requires db_owner Call made to sys.sp_replincrementlsnWill enabling CDC impact performance?Similar overhead to transactional replicationAsynchronous processing reduces overall impactIncreases data sizePrevents minimally logged operationsLess than 10% overhead with normal workload (and no IO issues)
  • 81. CREDIBLE CONSISTENT DATAA full suite of tools for enterprise information management (EIM)Help produce accurate,trustworthy dataDeliver credible, consistentdata to the right users withend-to-end dataintegration, cleansing anddata managementUse SQL Server forall EIM needs
  • 82. CLEANSE DATA WITH DATA QUALITY SERVICESTrusted decision makingBenefitsDelivers trusted information for BI and data warehousing workloadsCaptures data correction knowledge to collaborate on data qualityKey FeaturesMonitor, cleanse, match, profile your dataUniquely share data cleansing responsibilities between business and ITRuns as a standalone or leveraged with Integration Services (SSIS)Supports use of user-generated knowledge and IP by third-partyproviders connected to the cloud
  • 83. IT ALL BEGINS WITH YOUR DATA…
  • 84. DQS PROCESS
  • 85. KNOWLEDGE MANAGEMENT
  • 86. FIRST STEPS IN CREATING A KNOWLEDGE BASE
  • 87. DOMAIN RULES
  • 88. COMPOSITE DOMAIN (CD) – CORRECTION RULE
  • 89. COMPOSITE DOMAIN (CD) – VALIDATION RULE
  • 90. DEAL WITH MISSING DATA
  • 91. TERM-BASED RELATIONS (TBR)
  • 92. MS OFFICE SPELLER
  • 93. DQS KNOWLEDGE SOURCES
  • 94. DQS KNOWLEDGE SOURCES
  • 95. REFERENCE DATA SERVICES (RDS)DQS is using Reference Data Services for cleansing and enriching Addresses,Company Names, E-mails and Phones.Subscribe to reference data services via Windows Azure Marketplace or directlythrough the service providers.
  • 96. REFERENCE DATA SERVICES (RDS)- CONFIGURATIONSimple Configuration On The DQS Client ApplicationGet an account ID from Windows Azure Marketplace Data Market or directly from thereference data services provider.Add the key on the DQS Client Administration screen.
  • 97. RDS DEFINITION IN THE KNOWLEDGE BASEAttach one or more reference data services to domains orcomposite domains based on your data structure andbusiness requirement.
  • 98. CLEANSING WITH REFERENCE DATA SERVICESCleansing is interactive and simple. Results are classified to 5categories based on confidence level determined by the referencedata services and DQS Cleansing.
  • 99. KNOWLEDGE BASE ENRICHMENTNew knowledge gathered during the cleansing project is incorporateinto the relevant knowledge base, ensuring that trusted knowledge is notlost, and that the knowledge base is continually improved.
  • 100. SHARING KNOWLEDGE
  • 101. DATA MATCHING AND DE-DUPLICATIONBenefitsEnables creating a matching policyinteractively using a computer-assisted process.Ensures that values that areequivalent, but were entered in adifferent format or style, are in factrendered uniform.Identifies exact and approximatematches, enabling removal ofduplicate data.
  • 102. CLEANSING – SCENARIOEnforce standards with validation rules and pick-lists.Correct inaccuracies and inconsistenciesFind and replace bad or missing data
  • 103. MATCHING – SCENARIO
  • 104. DEPLOYMENT ARCHITECTURE
  • 105. CREDIBLE CONSISTENT DATAA full suite of tools for enterprise information management (EIM)Help produce accurate,trustworthy dataDeliver credible, consistentdata to the right users withend-to-end dataintegration, cleansing anddata managementUse SQL Server forall EIM needs
  • 106. MANAGE DATA WITH MASTER DATA SERVICESMaintain Master Data Across The Organization & Make It EasierFor End Users To Manage
  • 107. WHAT IS MASTER DATA?
  • 108. WHAT IS MASTER DATA?Non-Transactional list of Business DataNouns of the BusinessShared Across Multiple Business FunctionsNeeds to be Proactively Managed to RunBusinessIt is NOT VolatileIs Important DataNot all Important Data is Master Data
  • 109. WHY MASTER DATA?Continuous Quality ManagementEffective Data GovernanceCentral source for company’s definitional/dimensional dataEase of access for business usersSingle Version of the TruthEffective sharing (producing and consuming)
  • 110. MDS ARCHITECTURE
  • 111. MDS CAPABILITIES
  • 112. MDS PROCESS – 1 OF 2Create the ModelCreate the EntitiesBusiness EntitiesDBAs (Domain Based Attributes)Add Attributes for EntitiesAssign Attribute GroupsImport Supporting MembersBusiness Rules
  • 113. MDS PROCESS – 2 OF 2Import Primary MembersCreate Derived HierarchiesCreate Explicit HierarchiesCreate CollectionsCreate User-Defined MetadataLock model and assign Version FlagCreate Subscription ViewsConfigure User and Group Permissions
  • 114. MDS UIUI is divided into two main areasIW Worker tasks – for data stewards who are responsiblefor managing dataAdministrative tasks – for admins who are responsible forthe entities, model, attributes, business rules, subscriptionviews, users/groups and their permissionLogo can be customized(but its not supported)Logo file location – “c:Program FilesMicrosoft SQLServer110Master DataServicesWebApplicationsImageslogo.png & logo.jpg
  • 115. HIERARCHIESExplicit Store Owner/Operator Hierarchy - Explicit RootRagged (means leaf member could be at any level) RootUses only one entityConsolidated members are used to group other Company Owned (bucket) Organization Groups (bucket) Code: CO Code: OGconsolidated members and leaf members Name: Company Owned Name: Organization GroupsYou can manage the relationship within themembers without affecting any entities Stores Organization Group Code: <GroupCode>Derived Name: <GroupName>Level based (means leaf member always exist at Franchiseesame level regardless of the number of levels) Code: <FRCode> Name: <FR Name>Relationship between multiple entities – Parentto child Franchisee Head Operations ManagerEvery level corresponds to a specific domain-based Code: <FRHeadCode> Name: <FRHeadName> Code: <OMCode> Name: <OM Name>attribute (DBA) with the entityCan be recursive Consolidated Members Operations SupervisorTo change the relationship between the node, data Leaf Members Code: <OSCode> Name: <OS Name>have to be updated in corresponding entities
  • 116. HIERARCHIES (CONTD.)Hybrid of simple Derived Hierarchyand Recursive Derived HierarchyImport process in two pass:1. Import all records without any parents2. Import all records with update for ParentsAssociate Restaurant only withhighest level of Parents(Operator 0)Business Rule is used to update the Restaurantassociation to “Nothing” for non “0” levels
  • 117. EXCEL ADD-INMake sure to use right version of Excel Add-inFor Office 2007 – 32-bitFor Office 2010 x64 – 64-bitFor Office 2010 x86 – 32-bitOnce connected you can browse through all theentities from MDM modelPublish – publishes changes made in Excel into MDMDelete – marks record for deletion in MDMCombine Data – allows you to add/update data into MDM entityfrom external source of data (in another excel sheet)Apply Rules – applies business rules defined on an entityShow Status – shows the status if update were imported into MDMsuccessfully or notIt is very useful for creating entities as part of earlydevelopment phase – more for POC purposeHierarchies management is currently not supported
  • 118. BUSINESS RULESBR Sample -1: Concatenate ValuesUpdate Name with their Position Abbreviation
  • 119. BUSINESS RULES (CONTD.)BR Sample -2: Update ValuesUpdate Restaurant Status in [Restaurant] entity based on its Lifecycle event(Lifecycle-Status mapping defined in LifeCycleEvent entity)
  • 120. BUSINESS RULES (CONTD.)What else can you do? Create your own expressions
  • 121. BUSINESS RULES (CONTD.)Publish or PerishPublishing Business RulesUnpublished Rules DO NOT get Applied
  • 122. BUSINESS RULES (CONTD.)Now that you’ve published, you can applyAt Entity Level, BR can be Validated/Applied atanytime via the MDM UI (explorer) for each EntityAt Model Level, BR can also be Validated/Applied atanytime for the entire Model (All Entities) via SystemAdministration →Version ManagementAt Model Level, you can programmatically Validate/Applyusing the stored procedure:EXECUTE mdm.udpValidateModel @User_ID, @Model_ID, @Version_ID,
  • 123. SECURITYGranularity down to Attribute LevelFunctional SecurityExplorerVersion ManagementIntegration ManagementUser & Group PermissionsSystem AdministrationModel Object SecurityEntities, AttributesPermissions, Read Only, Update DenyHierarchy Member SecurityAny node of – Derived/Explicit hierarchyPermissions: Read-only, Update, or Deny
  • 124. SECURITYSlice and dice
  • 125. ENTITY BASED STAGING (EBS)
  • 126. ENTITY BASED STAGING (EBS) - CONTINUEDImport TypeFor details on Leaf Member Staging Table columns (must see!)http://msdn.microsoft.com/en-us/library/ee633854.aspx
  • 127. ENTITY BASED STAGING (EBS) - CONTINUED
  • 128. ENTITY BASED STAGING (EBS) - CONTINUEDUsage: SELECT * FROM stg.viw_name_MemberErrorDetailsStaging Process Error Codes and Descriptionhttp://msdn.microsoft.com/en-us/library/ff487022.aspx
  • 129. ENTITY BASED STAGING (EBS) – (CONTD.)
  • 130. SUBSCRIPTION VIEWS
  • 131. MAIN SCENARIOS
  • 132. MDS-DATA WAREHOUSE SCENARIO
  • 133. USE CASE SCENARIO FOR FOOD RETAILER Location People Association Data Stewards Owner/ Field Legal Operator Operations Ownership Hierarchy Hierarchy UI eb &W d-in ETL el A d ID Restaurant E xc Locations Provisioning Systems Location Data Crew Access Hours Of Microsoft Operations ETL MDM FIM Manager (for Crews only) or Microsoft ADFS Restaurant MD Characteristics S We bA PI ETL & on Su bs ati cri tic pti en on th Vie Au ws Crew HR Europe HR US & Canada system Systems HR Systems (Non- McDonald’s) Consumer Applications People Data
  • 134. SOLUTION ARCHITECTURE FOR FOOD RETAILER
  • 135. ETL ARCHITECTURE FOR FOOD RETAILER
  • 136. OPERATIONAL REPORTS
  • 137. MDM WITH DW/BI
  • 138. NEXT STEPS
  • 139. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademar ks 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 accu racy 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.

×