Advertisement
Check these out next
SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services
May. 17, 2012•0 likes•6,435 views
1 likes
Be the first to like this
Show More
views
Total views
0
On Slideshare
0
From embeds
0
Number of embeds
0
Download to read offline
Report
Technology
A comparison of two enterprise taxonomy store solutions as presented at the Orange County SharePoint Users' Group on May 16, 2012.
Henry OngFollow
DellAdvertisement
Advertisement
Advertisement
Recommended
Playing Tag: Managed Metadata and Taxonomies in SharePoint 2010Henry Ong
SharePoint 2010 Managed Metadata Service ApplicationMohamed Abdeen
KMA SharePoint Saturday San Francisco BIKnowledge Management Associates, LLC
SharePoint 2010 Managed MetadataNick Hobbs
SharePoint 2010 Managed Metadata ServiceCraig Pilkenton
SPSTCDC - Managed Metadata and Taxonomies in SharePoint 2010 - Playing TagKnowledge Management Associates, LLC
SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services
- SQL Master Data Services 2012 vs. SharePoint Managed Metadata Services A comparison of two enterprise taxonomy store solutions Henry Ong SharePoint Systems Administrator @ Quest Software 5/16/2012 ©2011 Quest Software, Inc. All rights reserved.
- Quest Market Presence Americas 60 Offices, 3 HQs EMEA APJa Sales/Mrkg 3600+ Employees R&D Support 178 Countries 100,000+ Customers All Verticals Global 200 SMB Multiple Business Lines Database, Monitoring, Data Protection, User Workspace/Virtualization, Windows (SharePoint, AD, Messaging), Identity Mgmt 1 ©2011 Quest Software, Inc. All rights reserved.
- Agenda • Brief overview of MMS & MDS • Usage scenarios • Pros/Cons • MDS + SharePoint integration points • Demos 2 ©2011 Quest Software, Inc. All rights reserved.
- Brief: SP 2010 Managed Metadata Service • Centralized enterprise repository for tag hierarchies and keywords • Publish and subscribe model for distributed content types • Promotes tagging ease of use and folksonomy 3 ©2011 Quest Software, Inc. All rights reserved.
- Brief: SQL Server 2012 Master Data Services • Centralized enterprise repository for tag hierarchies and keywords • Used to implement Master Data Management • Non-transactional “nouns” of the company • Aligns data across systems 4 ©2011 Quest Software, Inc. All rights reserved.
- Usage Scenarios: Managed Metadata Service • Primarily used in SharePoint • Capture social tagging • Capture structured metadata • Capture unstructured metadata/folksonomy • Autocomplete suggestions • Content Type Hub Syndications 5 ©2011 Quest Software, Inc. All rights reserved.
- Usage Scenarios: Master Data Services • System of record for other systems. − Ex: Vendor drop down in procurement system may consume from list of vendors in MDS. • Generation of Derived/Explicit Hierarchies − Derived = hierarchies derived from relationships defined in the MDS Entities – Ex: Product hierarchies that show what products belong to which BU. − Explicit = hierarchies that are set without regard to relationships defined in MDS. – Ex: Creation of alternate universes for modeling or reporting purposes. 6 ©2011 Quest Software, Inc. All rights reserved.
- SP 2010 Managed Metadata Services Pros Cons • Browser based management • No versioning is easier vs. MDS • No workflows/event hooks • Built in language variation capabilities • No UI for custom • More easily properties/attributes move, promote, deprecate, re use terms. • No concept of alternative hierarchies • Integrated SharePoint column • No offline/mass updating • Easier to setup multi- capabilities level/many-to-many relationships 7 ©2011 Quest Software, Inc. All rights reserved.
- SQL 2012 Master Data Services Pros Cons • Excel based management of data is awesome • Brand new platform/set of terminology to learn (from SP perspective) • Versioning and transaction history logging • Workflow integration not mature • Custom properties/attributes • Building multi-level/many-to-many relationships not as intuitive. • Field level security • To get anything out of it requires • Browser based view creation for consuming applications development • Business rules & workflow integration • Complete web services available OOTB • Built in adapters for BizTalk integration 8 ©2011 Quest Software, Inc. All rights reserved.
- SQL 2012 MDS + SharePoint Together • MDS can initiate workflows in SharePoint • Embed MDS inside of SharePoint 9 ©2011 Quest Software, Inc. All rights reserved.
- Demo Time! 10 ©2011 Quest Software, Inc. All rights reserved.
- Resources • Overview and Training Videos − http://msdn.microsoft.com/en-us/sqlserver/ff943581.aspx • Creating Custom Workflows − http://msdn.microsoft.com/en-us/library/hh270298.aspx • MDS Code Samples − http://sqlserversamples.codeplex.com/wikipage?title=SQL%20Server %202012%20Master%20Data%20Services%20&IsNewlyCreatedPa ge=true • MSDN Forum for MDS − http://social.technet.microsoft.com/Forums/en-US/sqlmds/threads 11 ©2011 Quest Software, Inc. All rights reserved.
- Contact Information • Twitter @henry_ong • http://blog.henryong.com • henry.ong@quest.com 12 ©2011 Quest Software, Inc. All rights reserved.
- ©2011 Quest Software, Inc. All rights reserved.
Editor's Notes
- We have offices throughout the world and have the resources to support the largest global organizations whether they be in the Americas, Europe, Middle East, Africa, or across the Asia Pacific and Japan region.
- A common example of poor MDM is the scenario of a bank at which a customer has taken out a mortgage and the bank begins to send mortgage solicitations to that customer, ignoring the fact that the person already has a mortgage account relationship with the bank. This happens because the customer information used by the marketing section within the bank lacks integration with the customer information used by the customer services section of the bank. Thus the two groups remain unaware that an existing customer is also considered a sales lead. The process of record linkage is used to associate different records that correspond to the same entity, in this case the same person.
Advertisement