SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

14
©2011 Quest Software, Inc. All rights reserved. Henry Ong SharePoint Systems Administrator @ Quest Software 5/16/2012 A comparison of two enterprise taxonomy store solutions SQL Master Data Services 2012 vs. SharePoint Managed Metadata Services

description

A comparison of two enterprise taxonomy store solutions as presented at the Orange County SharePoint Users' Group on May 16, 2012.

Transcript of SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

Page 1: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

©2011 Quest Software, Inc. All rights reserved.

Henry Ong

SharePoint Systems Administrator @ Quest Software

5/16/2012

A comparison of two enterprise taxonomy store solutions

SQL Master Data Services 2012 vs. SharePoint Managed Metadata Services

Page 2: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

2

©2011 Quest Software, Inc. All rights reserved.

AmericasEMEAAPJa

Sales/MrkgR&DSupport

178 CountriesAll VerticalsGlobal 200SMB

Database, Monitoring, Data Protection, User Workspace/Virtualization, Windows (SharePoint, AD, Messaging), Identity Mgmt

60 Offices, 3 HQs

3600+ Employees

100,000+ Customers

Quest Market Presence

Multiple Business Lines

Page 3: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

3

©2011 Quest Software, Inc. All rights reserved.

Agenda

• Brief overview of MMS & MDS

• Usage scenarios

• Pros/Cons

• MDS + SharePoint integration points

• Demos

Page 4: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

4

©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

Page 5: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

5

©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

Page 6: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

6

©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

Page 7: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

7

©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.

Page 8: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

8

©2011 Quest Software, Inc. All rights reserved.

SP 2010 Managed Metadata Services

Pros

• Browser based management is easier vs. MDS

• Built in language variation capabilities

• More easily move, promote, deprecate, reuse terms.

• Integrated SharePoint column

• Easier to setup multi-level/many-to-many relationships

Cons

• No versioning

• No workflows/event hooks

• No UI for custom properties/attributes

• No concept of alternative hierarchies

• No offline/mass updating capabilities

Page 9: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

9

©2011 Quest Software, Inc. All rights reserved.

SQL 2012 Master Data Services

Pros

• Excel based management of data is awesome

• Versioning and transaction history logging

• Custom properties/attributes

• Field level security

• Browser based view creation for consuming applications

• Business rules & workflow integration

• Complete web services available OOTB

• Built in adapters for BizTalk integration

Cons

• Brand new platform/set of terminology to learn (from SP perspective)

• Workflow integration not mature

• Building multi-level/many-to-many relationships not as intuitive.

• To get anything out of it requires development

Page 10: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

10

©2011 Quest Software, Inc. All rights reserved.

SQL 2012 MDS + SharePoint Together

• MDS can initiate workflows in SharePoint

• Embed MDS inside of SharePoint

Page 11: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

11

©2011 Quest Software, Inc. All rights reserved.

Demo Time!

Page 13: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

13

©2011 Quest Software, Inc. All rights reserved.

Contact Information

• Twitter @henry_ong

• http://blog.henryong.com

[email protected]

Page 14: SharePoint 2010 Managed Metadata vs SQL 2012 Master Data Services

©2011 Quest Software, Inc. All rights reserved.