More Related Content Similar to SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services (20) 1. 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.
2. 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.
3. Agenda
• Brief overview of MMS & MDS
• Usage scenarios
• Pros/Cons
• MDS + SharePoint integration points
• Demos
2
©2011 Quest Software, Inc. All rights reserved.
4. 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.
5. 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.
6. 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.
7. 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.
8. 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.
9. 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.
10. SQL 2012 MDS + SharePoint Together
• MDS can initiate
workflows in
SharePoint
• Embed MDS inside of
SharePoint
9
©2011 Quest Software, Inc. All rights reserved.
11. Demo Time!
10
©2011 Quest Software, Inc. All rights reserved.
12. 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.
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.
