16. SharePoint Database Size
MS recommended max: 200 GB
Customer max: 50 GB
Need full
backup/
restore,
so limits
still apply!
17. 20 GB
Portal
20 GB
Area 1
100
GB
Area 1 docs
100
GB
Area 1 docs
100
GB
Area 2 docs
100
GB
Area 2 docs
20 GB
Area 2
100
GB
Area 1 docs
Provisioning
sites using
PowerShell
Giving
impression
of hierarchy
using
PowerShell
18. 20 GB
Portal
20 GB
Area 1
100
GB
Area 1 docs
100
GB
Area 1 docs
100
GB
Area 2 docs
100
GB
Area 2 docs
20 GB
Area 2
100
GB
Area 1 docs
Demo
time
20. 20 GB
Portal
20 GB
Area 1
100
GB
Area 1 docs
100
GB
Area 1 docs
100
GB
Area 2 docs
100
GB
Area 2 docs
20 GB
Area 2
100
GB
Area 1 docs
21. Content
farm 20 GB
Portal
20 GB
Area 1
100
GB
Area 1 docs
100
GB
Area 1 docs
100
GB
Area 2 docs
100
GB
Area 2 docs
20 GB
Area 2
100
GB
Area 1 docs
Shared
Services
Farm
Search
Scope 1
Scope 2
22. Content
farm 20 GB
Portal
20 GB
Area 1
100
GB
Area 1 docs
100
GB
Area 1 docs
100
GB
Area 2 docs
100
GB
Area 2 docs
20 GB
Area 2
100
GB
Area 1 docs
Shared
Services
Farm
Search
Managed
Metadata:
Terms
Columns
Content
Types
All sites
subscribe
to the «hub»
to ensure
full sync
25. Document Set Evaluation
Pros
• Easy for end users
• No coding
• Better findability
• Promoted by Microsoft
Cons
• Not mature
• Little experience
anywhere
• One level only
31. Logging SHOULD be easy!
Log.error(«Hello world!»)
SPDiagnosticsService.Local.WriteTrace(
0,
new SPDiagnosticsCategory(
“Hello", TraceSeverity.Unexpected,
EventSeverity.Error),
TraceSeverity.Unexpected,
“Hello world”); }
The SharePoint version of «easy»...
33. Ideal logging:
Easy to write
No special
permissions
required
Remotely
accessible
Centralized
in a load
balanced
farm
Easy to turn
on/off at
runtime
34. Log to a SharePoint list!
public static void LogError(SPWeb web, string msg)
{
SPList logList = web.Lists.TryGetList("Logging");
if (logList != null) {
var logItem = logList.Items.Add();
logItem["Title"] = msg;
logItem.Update();
}
}
Simple interface
Easy on/off
Standard list
I et land med mer papirbaserte prosesser.
Partnere med papirbaserte løsninger som vi (Statoil) må forholde oss til.
Forklare mer om hva løsningen skal løse. Hva er arbeidsflyten osv. (Saksbehandling, søknader på områder osv.)
Få frem at koding kunne være fristende pga. spesielle behov.
Eskil jobbe tett med kundene - forstå dokumentstruktur og metadata
Gjorde også valg av arkitektur og plattform
Line kom inn litt senere, og jobbet tett med Eskil. Ingen av dem i nærheten av å kode.
Erstatter XXX from SharePoint 2007
Veldig lite informasjon å finne på blogger o.l.!
RBS-scenarier: streaming, avoid duplicate storage, low-cost media
Fun fact: you CAN create doc-sets inside doc-sets using code. For all practical matters, it seems to work fine!
Customer wish – not requirement
No support for centralized logging
And, for logging to the Windows Event log, you need a local registry setting to be added!
Both ULS and Windows Event log also requires local access or similar to the physical server, and is hard to track in a load balanced environment.
But, fortunately, a colleague had given me an idea for a simpler solution.
Note that «SPWeb» is required when logging in event receivers, otherwise it can be deducted via the context object.
Invest in understanding the scenario
Invest in understanding SharePoint «Out of the Box»
RBS is not a panacea
Document Sets are great, and will probably get better
Beware of coding – log to lists
Size matters