Turn on more accessible mode

Turn off more accessible mode

Skip Ribbon Commands

Skip to main content

Tales from a SharePoint farm

SharePoint Facts All Items

SharePoint Facts

Help (new window)

All Site Content

		Fact	Source
		At its core, SharePoint Foundation is a provisioning engine	Inside Microsoft SharePoint 2010
		"STS" stands for "SharePoint Team Services"	SharePoint 2010 Professional Administration
		"vti" stands for Vermeer Technologies, Inc., the company that created FrontPage	Various sources
		20 Web applications per SP2010 farm is a reasonable upper limit	Spencer Harbars
		The client-side object model was introduced in SharePoint 2010.	Inside Microsoft SharePoint 2010
		SharePoint 2010 projects must be configured to target .NET Framework 3.5	Inside Microsoft SharePoint 2010
		SharePoint 2010 is 64-bit only, no exceptions.	Technet
		Never access the SharePoint configuration database or any of the content databases directly. Use the OM.	Inside Microsoft SharePoint 2010
		The MSFT recommended limit of 10 applies to content application pools only, not service endpoints.	Spencer Harbars
		16 GB RAM is recommended for DB servers in medium sized SP2010 farms.	Technet
		Pre-grow SP2010 content databases for performance reasons.	Technet
		A SP2010 Standard FIS license is limited to a single AD domain and related subdomains.	sharepoint.microsoft.com
		BLOB caching can be used with host-named site collections in SP2010.	SharePoint Server Caches Overview
		Use an XML webpart with XSL to create a RSS feed viewer in SP2010 Foundation.	Dux Raymond
		Restoring a SharePoint SQL config DB backup is NOT supported, so ensure you document/backup your farm settings!	Sean McDonough
		Look after your SQL tempdb. It is used constantly!	Michael Noel
		Splitting your tempdb for performance should be based on physical - not virtual - CPU cores.	Michael Noel
		SQL Server 2008 R2 is strongly recommended over RTM for performance reasons.	Michael Noel
		Implement a 1:1 ratio of physical to virtual cores in your virtualised SP2010 farm for performance.	Michael Noel
		Office 365 represents a shift from capital expenditure to operational expenditure.	Matt Groves
		Following an upgrade to SP2010, you can still switch back to V3 visuals using PowerShell.	Todd Klindt
		A feature instance is what gets created when a user activates your feature definition.	Inside Microsoft SharePoint 2010
		SharePoint creates feature instances with entries in either a content db or the config db depending upon feature activation scope.	Inside Microsoft SharePoint 2010
		The only file that is required for every feature definition is the feature manifest file that must be named feature.xml.	Inside Microsoft SharePoint 2010
		The 4 possible feature activation scopes are Web, Site, WebApplication and Farm.	Inside Microsoft SharePoint 2010
		SharePoint does not allow two versions of a feature definition to be installed side by side within the same farm: Updated versions overwrite earlier versions.	Inside Microsoft SharePoint 2010
		The only way to back up your AAM configuration is to document it	Spencer Harbars
		SP2010 automates SQL index defragmentation & statistics maintenance	"Database Maintenance for Microsoft® SharePoint® 2010 Products"
		The DBCC CHECKDB command should be run on SharePoint DBs once a week.	"Database Maintenance for Microsoft® SharePoint® 2010 Products"
		Do not auto-shrink databases or configure a maintenance plan that programmatically shrinks your databases.	"Database Maintenance for Microsoft® SharePoint® 2010 Products"

1 - 30

Next

© Copyright 2010 Benjamin Athawes. Site powered by fpweb.net.