Notes Chapter 2 – Sharepoint 2010 Unleashead

 

All SharePoint content is stored in databases, including all document library content, list items, document metadata, and web parts. There are only two exceptions to this. The first is if the database server uses a concept known as Remote BLOB Storage (RBS), which allows for the storage of the documents, or BLOBs (binary large objects), in another storage medium such as a file server or an archive.

The full-text search index, which is stored in flat-file format

Supported versions of SQL Server for SharePoint 2010 are as follows:

. SQL Server 2005 SP3 x64

. SQL Server 2008 x64

. SQL Server 2008 R2 x64

A SharePoint Web Server Role runs on either Windows Server 2008 x64 IIS 7.0 or, preferably, Windows Server 2008 R2 x64 IIS 7. In both cases, SharePoint 2010 requires specific roles to be installed in advance of installation, including the following components:

. Application Server Role

. Web Server (IIS) Role

. Microsoft SQL Server 2008 Native Client

. Windows Identity Foundation (KB974405)

. Microsoft Sync Framework Runtime v 1.0 (x64)

. Microsoft Chart Controls for Microsoft .NET Framework 3.5

. Microsoft Filter Pack 2.0

. Microsoft SQL Server 2008 Analysis Services ADOMD.NET

. Microsoft Server Speech Platform Runtime (x64)

. Microsoft Server Speech Recognition Language—TELE

Load balancing can be either hardware-based or software-based using Windows Network Load Balancing (NLB), fully supported for SharePoint web role servers.

the index corpus can range from 5 percent to 30 percent of the size of content being indexed, so be sure to include a large enough index disk drive for your index server.

There are a few things to note about SharePoint search:

. Search in SharePoint is security-trimmed for supported content, excluding some external content sources. This means that end users will get search results only from content that they have rights to access. This is a highly useful feature that prevents users from seeing content to which they don’t have access.

. Although search is security-trimmed, the permissions are reevaluated only after performing a full crawl of content. Subsequently, if someone is removed from having permissions to a document, she can still see the text of that document as part of a search until a full, not an incremental, crawl has been performed.

. Because SharePoint 2010 allows for redundant search and indexing capability, any one server being down does not take down the entire environment, assuming the search service application is running on more than one server.

For security reasons, it is not generally recommended to have an internal SharePoint document management or intranet environment directly accessible from the Internet unless it is secured by an advanced reverse proxy platform such as Microsoft’s Forefront Edge line that includes the Threat Management Gateway or Unified Access Gateway products.

At least 1GB of bandwidth with less than 1ms of latency between offices located relatively close to one another,

There is no native way to do two-way replication of content between farms with SharePoint 2010.

All SharePoint server roles, with the exception of the database role, can only be a member of a single farm.

Generally recommended to limit the number of content databases on a single SQL instance to no more than 50.

All farm members must have near-full network connectivity (1Gb+ Bandwidth, <1ms latency) to all other farm members, with a large number of open ports with nearly all of them open.

The heaviest hitter of all the SharePoint roles is the SQL database server role.

The search service application role, for example, which is responsible for creating a full-text searchable index for search, is the heaviest hitting of the SharePoint roles, excluding, of course, the database role.

The search service application role also requires enough drive space to physically store the index files, which are essentially copies of all text that has been crawled across all data sources. The size of this index can range from 5 percent to 30 percent of the total size of the searchable content being crawled. For example, if SharePoint is configured to search a file share (Exchange public

folders, and websites), and that file share contains 100GB of office documents, the index size will total between 5GB and 30GB, depending on how much actual text is stored in the documents.

Typically web role servers will have between 8GB and 12GB of RAM in most cases, and at least two cores allocated to it.

All servers in a SharePoint farm require the Windows Server operating system. The following versions of Windows Server are supported:

. Windows Server 2008, Standard or Enterprise, x86 or x64

. Windows Server 2008 R2, Standard or Enterprise, x86 or x64

An alternative to Windows Server 2008 R2 is Windows Server 2008 SP1.

Windows Server 2008 R2 Enterprise es el recomendado para el rol de web server de Sharepoint 2010 SharePoint databases must be installed on 64-bit SQL servers, and they can be successfully installed on the following types of SQL servers:

. SQL Server 2005 x64 SP3, Standard or Enterprise

. SQL Server 2008 x64 SP1, Standard or Enterprise

. SQL Server 2008 R2 x64, Standard or Enterprise

It is highly recommended to consider SQL Server 2008 R2 for the SharePoint database role because it provides for the most robust, capable, and secure platform for SharePoint. In

addition, it includes features that are useful for SharePoint, such as PowerPivot and Transparent Data Encryption (TDE), which enables the SharePoint databases to be stored in encrypted format.

SQL Server 2008 R2 X64 Enterprise for SharePoint is highly recommended.

SharePoint 2010 includes an antivirus API that enables all documents to be scanned for viruses by a compliant antivirus engine. ForeFront Protection for SharePoint (FPSP)

The most common add-on for SharePoint search are iFilters. Index iFilters provide specific knowledge for the SharePoint indexer on how to break open specific file types and index the text content within them.

Use the latest version of SQL Server, SQL Server 2008 R2, whenever possible, particularly to take advantage of features such as PowerPivot, which are only provided with that version of SQL Server.

Consider separating the service application roles from the web role servers to improve performance.

Consider best-practice security approaches such as SQL Server Transparent Data Encryption (TDE) for storage security, IPsec and SSL Certificates for transport secu-

rity, and Active Directory Rights Management Services (AD RMS) for Data Loss Prevention.

Consider database mirroring for the content databases to provide for both highavailability and disaster recovery of SharePoint content.

Be sure to allocate enough hard drive space for the Search Service Application roles for the index corpus; allocate 5 percent to 30 percent of the size of the data being indexed.

Use clustering and network load balancing to scale the SharePoint server environment and provide redundancy.

to get SQL services to run, you must create a manual Windows firewall port rule that enables port 1433,

By default, some SQL Server installations do not have TCP/IP enabled for remote access. This is required for use by a remote SharePoint server.

Consider the use of a SQL alias for the database server name so that it can be easily changed in the future.

Enter a Database Access Account that has DBCreator and Securityadmin rights on the SQL Instance.

Keep this passphrase in a safe place; it is needed to add any additional servers to the farm in the future.

For long-term production support, however, Kerberos, SSL, and a default port of 443 are highly recommended for the SharePoint central web application.

 

http://www.amazon.com/Microsoft-SharePoint-2010-Unleashed-Michael/dp/0672333252