Http:// Travis Clayton Senior Consultant Microsoft Enterprise Services.

http://www.azsharepointpros.com

GROWING SHAREPOINT FROM SMALL LIBRARIES TO LARGE SCALE REPOSITORIES AND MASSIVE ARCHIVES

Travis ClaytonSenior ConsultantMicrosoft Enterprise Services


Agenda Session Flow

Front end: Talk about tools for end users to manage and find information in a sea of documents

Start with a small library and build up to a massive archive

Takeaways SharePoint 2010 is an indispensible tool for

data scale challenges Usability is essential to scalability Plumbing is taken care of automatically


SharePoint Grow Up ScenariosN

um

ber

of

inst

an

ces

Number of items

Team Site

Enterprise Metadata

and Content Types

Managed Library

Knowledge Base or Records Center

Massive Distributed

Archive


Key CharacteristicsUsed for small projects and teamsLots of these created ad hoc throughput the enterpriseMust be lightweight to create with little configuration steps

Scale Point 1: Ad Hoc Team Library

Library for storing a

small team’s work in progress

docs

A library spun up for a particular

project

Library size?Who manages the content?How does content get added?

100-200 docs

No manager

Ad hoc uploads

Examples:


DEMOTeam Library


Scale Point 1: Ad Hoc Team Library

Automatic participation with enterprise

doc lifecycle

SP2010 breaks the Site Collection Boundary

Enterprise Metadata and Content Types

Key takeaways from what we

just saw


Key CharacteristicsMore structure than a team site Probably one managed library per divisionToo big to find content without structure/planned navigationContent is important enough that users are willing to file correctly (if it’s still easy and adds value)

Scale Point 2: Managed Library

RFP Response

library for a sales force

Spec library for an

engineering team


Hundreds or thousands of docsInformally by subject ownerUpload and iterate until finished

Examples:Brand

images repository

for marketing


DEMOManaged Library


Scale Point 2: Managed Library

The system helps the user discover the

right metadata

Structured taxonomies allows virtual folders

and new content discovery paradigms

Key takeaways from what we

just saw


Key CharacteristicsUsers feel like they are handing off content to the archiveMostly finished work product, meant for broad consumptionSometimes, end users don’t even know what they are looking for

Scale Point 3: Repository/Archive

Corporate records archive

Knowledge management repository


Millions to tens of millions of docsA dedicated team

of content stewardsSubmission experience

Examples:Centralized

best practices repository


DEMOCorporate Archive


Scale Point 3: Repository/ArchiveKey takeaways from what we just saw

Indices are auto-managed and folder

structure is determined by

business needs

Content organizer ensures structure and

policies on the backend

Tag: AfterFY05, Contract

Folder Name: Post-Merger Contracts

Content Query, Search, and metadata

navigation help users answer broad,

unstructured questions


Key CharacteristicsLots of process automation to deal with high volumeBackend systems, not users, are primary submitterLogical organization and hierarchy is key

Scale Point 4: Massive, Distributed Archive

Archive for a large

government agency

Yearly archive of insurance

forms


Hundreds of millions of docs

Dedicated team

Automated processes

Examples:


Scale Point 4: Massive, Distributed Archive

Scale is achieved with a distributed architecture

Content organizer can route content to correct site collection in the archive

Content type

syndication enables central management

of distributed archive FAST search is used

to retrieve content

FY07 …

Hub

Enterprise Metadata and Content Types

Consistent types and policies

across the archive

If created in FY07…

FY08


Throughout the talk, I’ve mentioned a few back end scale improvements that make new scenarios in 2010 easy:

Reality Check: Review of Back End Scale Improvements

For more info on the back end of scale, see Technet:

Performance and capacity test results and recommendationsSharePoint Server 2010 capacity management: Software boundaries and limits

Internal database

improvements (e.g. lock ordering,

throttling, IOPS efficiency)

SQL 2008’s Remote Blob Storage (RBS)

decreased size of content DB

Compound indexing, index management,

and content-by-query

optimizations

Background per-item

processing throughput

maximization

http://technet.microsoft.com/en-us/library/ff608068.aspx

http://technet.microsoft.com/en-us/library/ff608068.aspx

http://technet.microsoft.com/en-us/library/cc262787.aspx

http://technet.microsoft.com/en-us/library/cc262787.aspx


Wrapping Up…N

um

ber

of

inst

an

ces

Number of items

Team Site

Enterprise Metadata

and Content Types

Managed Library

Knowledge Base or Records Center

Massive Distributed

Archive

Archive onauto-pilot

Team sites acting in coordination

Virtual folders organize the data

Tens of millions of

docs in a single list

Key TakeawaysSharePoint 2010 is an indispensible tool for data scale challengesUsability is essential to scalabilityPlumbing is taken care of automatically



Date post:	18-Jan-2016
Category:	Documents
Upload:	lucinda-gibbs
View:	213 times
Download:	1 times

Http:// Travis Clayton Senior Consultant Microsoft Enterprise Services.

Documents