Czech Information Worker Community

Microsoft Technet hosts lot of documents about SharePoint, one of them is the “SharePoint Server 2010 capacity management: Software boundaries and limits” which describes software boundaries and limits of Microsoft SharePoint Server 2010.

Below is article index and some interesting points:

Basic definitions:

Boundaries: Static limits that cannot be exceeded by design

Thresholds: Configurable limits that can be exceeded to accommodate specific requirements

Supported limits: Configurable limits that have been set by default to a tested value.

Index:

Overview of boundaries and limits,
Article contains information to help you understand the tested performance and capacity limits of SharePoint Server 2010, and offers guidelines for how limits relate to acceptable performance. The test results and guidelines provided in article apply to a single SharePoint Server 2010 farm. Adding servers to the installation might not increase the capacity limits of the objects that are listed

• Boundaries, thresholds and supported limits
  In SharePoint Server 2010, there are certain limits that are by design and cannot be exceeded, and other limits that are set to default values that may be changed by the farm administrator. There are also certain limits that are not represented by a configurable value, such as the number of site collections per Web application.
• How limits are established
• The Equalizer Metaphor

Limits and boundaries

• Limits by hierarchy
  • Web application limits
    300 Content databases per Web application
    5 Zones per Web application
    20 Managed paths per Web application
  • Web server and application server limits
    10 Application pools per Web server
    
  • Content database limits
    200 GB per content database
    Content database sizes up to 1 terabyte are supported only for large, single-site repositories and archives with non-collaborative I/O and usage patterns, such as Records Centers.
    When SharePoint Server 2010 is configured to use RBS, and the BLOBs reside on NAS storage, consider the following boundary. From the time that SharePoint Server 2010 requests a BLOB, until it receives the first byte from the NAS, no more than 20 milliseconds can pass
  • Site collection limits
    A site collection should not exceed 100 GB unless it is the only site collection in the database.
    
  • List and library limits
    List row size 8,000 bytes
    30,000,000 Documents per library
    30,000,000 Items per list
    Rows size limit: 6 table rows internal to the database used for a list or library item
    List view lookup threshold: 8 join operations per query
    List view threshold: 5000 items
    Coauthoring in Microsoft Word and Microsoft PowerPoint for .docx, .pptx and .ppsx files : 10 concurrent editors per document
  • Column limits
  • Page limits
  • Security limits
    Security principal: size of the Security Scope: 5,000 per Access Control List (ACL)
• Limits by feature
  • Search limits
  • User Profile Service limits
  • Content deployment limits
  • Blog limits
  • Business Connectivity Services limits
  • Workflow limits
  • Visio Services limits
  • PerformancePoint Services limits
  • Word Automation Services limits
  • SharePoint Workspace limits
  • OneNote limits
  • Office Web Application Service limits
  • Project Server limits

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

Download contains a two Windows Server 2008 R2 Hyper-V Virtual Machine set for evaluating and demonstrating Office 2010, SharePoint 2010 and Project Server 2010.

Virtual machine “a” contains the following pre-configured software:

1. Windows Server 2008 R2 Standard Evaluation Edition x64, running as an Active Directory Domain Controller for the “CONTOSO.COM” domain with DNS and WINS
2. Microsoft SQL Server 2008 R2 Enterprise Edition with Analysis, Notification, and Reporting Services
3. Microsoft Office Communication Server 2007 R2
4. Microsoft Visual Studio 2010
5. Microsoft SharePoint Server 2010 Enterprise Edition
6. Microsoft Office Web Applications
7. Microsoft FAST Search for SharePoint 2010
8. Microsoft Project Server 2010
9. Microsoft Office Professional Plus 2010
10. Microsoft Visio 2010
11. Microsoft Project 2010
12. Microsoft Office Communicator 2007 R2

Virtual machine “b” contains the following pre-configured software:

1. Windows Server 2008 R2 Standard Evaluation Edition x64, joined to the “CONTOSO.COM” domain
2. Microsoft Exchange Server 2010

http://www.microsoft.com/downloads/details.aspx?FamilyID=751fa0d1-356c-4002-9c60-d539896c66ce&displaylang=en

http://technet.microsoft.com/en-us/library/cc263199%28office.14%29.aspx

Models

Models are 34-by-44-inch posters that detail a specific technical area. These models are intended to be used with corresponding articles on TechNet. These models are created by using Office Visio 2007. You can modify the Visio files to illustrate how you plan to incorporate Microsoft SharePoint 2010 Products in your own environment.

SharePoint 2010 Products Deployment

Visio (http://go.microsoft.com/fwlink/?LinkId=183024)

PDF (http://go.microsoft.com/fwlink/?LinkId=183025)

XPS (http://go.microsoft.com/fwlink/?LinkId=183026)

Presents such deployment-related information as the different deployment stages and environments, plus a flowchart that illustrates the steps for installing and configuring SharePoint 2010 Products.

Services in SharePoint 2010 Products

Visio (http://go.microsoft.com/fwlink/?LinkID=167090)

PDF (http://go.microsoft.com/fwlink/?LinkID=167092)

XPS (http://go.microsoft.com/fwlink/?LinkID=167091)

Describes and illustrates the services architecture, including and common ways to deploy services in your overall solution design.

Cross-farm Services in SharePoint 2010 Products

Visio (http://go.microsoft.com/fwlink/?LinkID=167093)

PDF (http://go.microsoft.com/fwlink/?LinkID=167095)

XPS (http://go.microsoft.com/fwlink/?LinkID=167094)

Illustrates how to deploy services across farms to provide centralized administration of services.

Topologies for SharePoint Server 2010

Visio (http://go.microsoft.com/fwlink/?LinkID=167087)

PDF (http://go.microsoft.com/fwlink/?LinkID=167089)

XPS (http://go.microsoft.com/fwlink/?LinkID=167088)

Describes common ways to build and scale farm topologies, including planning which servers to start services on.

Hosting Environments in SharePoint 2010 Products

Visio (http://go.microsoft.com/fwlink/?LinkID=167084)

PDF (http://go.microsoft.com/fwlink/?LinkID=167086)

XPS (http://go.microsoft.com/fwlink/?LinkID=167085)

Summarizes the support for hosting environments and illustrates common hosting architectures.

Search Technologies for SharePoint 2010 Products

Visio (http://go.microsoft.com/fwlink/?LinkID=167731)

PDF (http://go.microsoft.com/fwlink/?LinkID=167733)

XPS (http://go.microsoft.com/fwlink/?LinkID=167732)

Compares and contrasts the search technologies that work with SharePoint Products 2010:

• SharePoint Foundation 2010
• Search Server 2010 Express
• Search Server 2010
• SharePoint Server 2010
• FAST Search Server 2010 for SharePoint

Search Environment Planning for Microsoft SharePoint Server 2010

Visio (http://go.microsoft.com/fwlink/?LinkID=167734)

PDF (http://go.microsoft.com/fwlink/?LinkID=167736)

XPS (http://go.microsoft.com/fwlink/?LinkID=167735)

Walks through primary architecture design decisions for search environments.

Search Architectures for Microsoft SharePoint Server 2010

Visio (http://go.microsoft.com/fwlink/?LinkID=167737)

PDF (http://go.microsoft.com/fwlink/?LinkID=167739)

XPS (http://go.microsoft.com/fwlink/?LinkID=167738)

Details the physical and logical architecture components that make up a search system and illustrates common search architectures.

Design Search Architectures for Microsoft SharePoint Server 2010

Visio (http://go.microsoft.com/fwlink/?LinkID=167740)

PDF (http://go.microsoft.com/fwlink/?LinkID=167742)

XPS (http://go.microsoft.com/fwlink/?LinkID=167741)

Walks through the initial design steps to determine a basic design for a SharePoint Server 2010 search architecture.

Business Connectivity Services Model

Visio (http://go.microsoft.com/fwlink/?LinkId=165565)

PDF (http://go.microsoft.com/fwlink/?LinkID=165566)

XPS (http://go.microsoft.com/fwlink/?LinkId=165571)

Microsoft Business Connectivity Services are a set of services and features in Microsoft SharePoint Server 2010 and Microsoft SharePoint Foundation 2010 that support integrating data from external systems into solutions based on Microsoft SharePoint Server and Microsoft SharePoint Foundation. This model poster describes the architecture of Microsoft Business Connectivity Services in SharePoint Server 2010 and provides information about how to create solutions that are based on the service.

Use this model with the following article: Business Connectivity Services overview (SharePoint Server 2010)

Content Deployment in SharePoint Server 2010

Visio (http://go.microsoft.com/fwlink/?LinkID=179391&clcid=0×409)

PDF (http://go.microsoft.com/fwlink/?LinkID=179523&clcid=0×409)

XPS (http://go.microsoft.com/fwlink/?LinkID=179524&clcid=0×409)

This model describes the content deployment feature in SharePoint Server 2010. It includes information about the following:

• Overview of content deployment
• Description of content deployment paths and jobs
• When to use content deployment
• Alternatives to content deployment
• Illustrates common content deployment farm topologies
• Illustrates and explains the overall content deployment process

Microsoft SharePoint Server 2010 Upgrade Planning

Visio (http://go.microsoft.com/fwlink/?LinkId=167098)

PDF (http://go.microsoft.com/fwlink/?LinkId=167099)

XPS (http://go.microsoft.com/fwlink/?LinkId=167100)

This model covers planning for an upgrade from Microsoft Office SharePoint Server 2007 to SharePoint Server 2010. It includes information about the following:

• Upgrade requirements: Hardware, operating system, and database
• Upgrade process: specific steps to follow before, during, and after the upgrade

Use this model with the following article: Upgrading to SharePoint Server 2010

Microsoft SharePoint Server 2010 Upgrade Approaches

Visio (http://go.microsoft.com/fwlink/?LinkId=167101)

PDF (http://go.microsoft.com/fwlink/?LinkId=167102)

XPS (http://go.microsoft.com/fwlink/?LinkId=167103)

This model helps you understand the in-place, database attach, and hybrid approaches to upgrading from Office SharePoint Server 2007 to SharePoint Server 2010.

• See the farm topologies before, during, and after upgrade
• Compare the advantages of each type of upgrade approach

Use this model with the following articles:

• Determine upgrade approach (SharePoint Server 2010)
• Upgrade process overview (SharePoint Server 2010)

Microsoft SharePoint Server 2010 — Test Your Upgrade Process

Visio (http://go.microsoft.com/fwlink/?LinkId=167104)

PDF (http://go.microsoft.com/fwlink/?LinkId=167105)

XPS (http://go.microsoft.com/fwlink/?LinkId=167106)

This model explains the methodology for testing the upgrade process before upgrading from Office SharePoint Server 2007 to SharePoint Server 2010.

• Understand the goals for testing your upgrade process: customizations, hardware, timing, planning
• See specific steps to follow for testing your upgrade process

Use this model with the following article: Use a trial upgrade to find potential issues (SharePoint Server 2010)

Microsoft SharePoint Server 2010 — Services Upgrade

Visio (http://go.microsoft.com/fwlink/?LinkId=167107)

PDF (http://go.microsoft.com/fwlink/?LinkId=167108)

XPS (http://go.microsoft.com/fwlink/?LinkId=167109)

This model covers upgrading services from Office SharePoint Server 2007 to SharePoint Server 2010.

• Considerations for specific services: Personalization, Search, InfoPath Forms, Excel, Business Data Catalog, Single Sign-on
• In-place upgrade with services
• Database attach upgrade with services

Getting started with business intelligence in SharePoint Server 2010

Visio (http://go.microsoft.com/fwlink/?LinkId=167082)

PDF (http://go.microsoft.com/fwlink/?LinkId=167170)

XPS (http://go.microsoft.com/fwlink/?LinkId=167171)

This model covers an overview of business intelligence in SharePoint Server and provides you with the following information.

• An overview of each business intelligence service and when you might use the service.
• Architecture for application of the business intelligence services and how they work together in a topology.
• A list of possible data sources for each business intelligence service.

In this blog post, Erika Ehrli announced start of a series of posts that will guide you through the most interesting 2010 features and resources available for developers.

Now starts by introducing the top places/content which recommends if you want to learn more about Office 2010 and SharePoint 2010 development.

http://blogs.msdn.com/erikaehrli/archive/2010/02/08/what-s-new-for-developers-in-office-2010-and-sharepoint-2010.aspx

Jeff Dalton: Adventures In SharePoint Land : http://sharepoint.nailhead.net/2010/02/unhandled-exceptions-that-can-crash.html

His team discovered some nastiness with unhandled exceptions inside their custom SharePoint code. Specifically they found that unhandled exceptions inside of SharePoint.Publishing.LoginRunningOperationJob can result an IIS Application Pool crash.

The reason is because this class puts the delegate code onto a separate thread that when aborted can leave the Application Pool in an unstable state. Which can (and does) result in an Application Pool recycle (which is bad for very large SharePoint sites that take a few minutes to spin-up).

So you need to make sure that your delegate code is wrapped in try/catch and do NOT throw the error from inside your catch (same as unhandled exception).

Summary: Walk through how to customize the Content Query Web Part (CQWP) in Microsoft Office SharePoint Server 2007 to query content across multiple sites in a site collection and display the results in any way that XSL can support. Learn how to get similar results when customizing the CQWP does not meet your needs. (20 printed pages)

  Robert Bogue, Thor Projects

January 2010

Applies to: Microsoft Office SharePoint Server 2007

Download the code samples that accompany this article: SharePoint Content Query Web Part Examples

Contents

• Introduction to SharePoint Content Query Web Part Customization
• Scenario: Crafting Custom Queries for the Content Query Web Part
• Customizing the Content Query Web Part Using the UI and the *.webpart File
• Deriving a Class for the Content Query Web Part
• Replacing the Content Query Web Part with SPSiteDataQuery or Search
• Conclusion
• Additional Resources

http://msdn.microsoft.com/en-us/library/ff380147.aspx

 http://msdn.microsoft.com/en-us/library/ms473633.aspx

There are many posts out there extolling the virtues of using metadata over folders for organizing information in SharePoint 2007. I certainly believe that metadata is a great tool for for classifying information, but it is incorrect to ask whether to use folders or metadata to organize information. Rather, it is more appropriate to ask when to use folders and when to use metadata. This post is not intended to be an in-depth discussion of information architecture. Instead, I wanted to provide a few pointers on when to use folders and when to use metadata. The following is a brief comparison between folder and metadata capabilities in the SharePoint platform. The context of the comparison is only out-of-the-box (OOTB) capabilities. With enough custom code, folders and metadata could be made equivalent.

	Folders	Metadata
Security	Folders can be used to propagate permissions and control the access to the resources the folders contain.	None.
Content Type Order	Folders can control which content types users can create using the New menu on the list toolbar. Folders can also control the order in which the content types appear in the menu.	None.
Navigation	Folders are intrinsically part of the navigational infrastructure in the SharePoint platform.	Metadata can be used to control navigation, but this requires creative approaches. List View web parts showing filtered list views can provide metadata-based navigational capabilities. While this requires no custom code, it can be labor intensive to add the web parts to a large number of pages. Additional metadata-based navigation can be accomplished through custom code.
Url	Folder names form portions of the Urls of the SharePoint resources the folders contain.	None.
Tools Support	Most Microsoft and 3rd party tools inherently know how to work with folders in the SharePoint platform.	Metadata support in 3rd party tools is spotty. While a tool from one vendor will generally understand how to handle its own metadata, the tool will generally not understand how to handle the metadata from another vendor’s tool. This can make it challenging to incorporate metadata from multiple vendors’ tools into a single SharePoint information architecture.
Search	None.	Metadata is indexed by SharePoint search and will return results based on keyword searches. MOSS 2007 also supports promoting selected metadata to searchable properties.
Sort	None.	Metadata can be used to control the order in which items are displayed in list views.
Filter	List views can be configured to show only the list items contained within a folder and its sub folders.	Metadata can be used to control the which items are displayed in list views.
Group	None.	Metadata can be used to group list items together in list views. List views limit grouping to two hierarchical levels.

original post on http://networkedblogs.com/p25674007 by Eugene Rosenfeld

This resource contains three text files that list all of the deprecated types and methods in Microsoft SharePoint Server 2010 and Microsoft Office SharePoint Server 2007.

• SPS2010NewlyDeprecated.txt lists the types and methods that have been made obsolete in Microsoft SharePoint Server 2010 since the release of Microsoft Office SharePoint Server 2007.
• SPS2010Deprecated.txt lists all of the types and methods that are obsolete in Microsoft SharePoint Server 2010.
• OfficeSharePointServer2007Deprecated.txt lists all of the types and methods that are obsolete in Microsoft Office SharePoint Server 2007.

Obsolete types and methods will continue to work in your custom code and solutions, but they will generate compiler warnings, and you should update your code to use the new types and methods as indicated by the compiler warnings. The compiler warnings for each type and method are listed in the files in this resource.

Note: Types and methods in the Microsoft.SharePoint.Portal namespace are not included in these lists because, with a few exceptions, the entire namespace has been made obsolete.

http://code.msdn.microsoft.com/sps2010deprecated

download contains a two Virtual Machine set for evaluating and demonstrating Office 2010 and SharePoint 2010.

Virtual machine “a” contains the following pre-configured software:

1. Windows Server 2008 SP2 Standard Edition x64, running as an Active Directory Domain Controller for the “CONTOSO.COM” domain with DNS and WINS
2. Microsoft SQL Server 2008 SP2 Enterprise Edition with Analysis, Notification, and Reporting Services
3. Microsoft Office Communication Server 2007 R2
4. Visual Studio 2010 Beta 2 Ultimate Edition
5. Microsoft SharePoint Server 2010 Enterprise Edition Beta 2
6. Microsoft Office Web Applications Beta 2
7. FAST Search for SharePoint 2010 Beta 2
8. Microsoft Project Server 2010 Beta 2
9. Microsoft Office 2010 Beta 2
10. Microsoft Office Communicator 2007

Virtual machine “b” contains the following pre-configured software:

1. Windows Server 2008 R2 Standard Evaluation Edition x64, joined to the “CONTOSO.COM” domain
2. Microsoft Exchange Server 2010

Active directory has been preconfigured over 200 “demo” users with metadata in an organizational structure. All of these user profiles have been imported and indexed for search within SharePoint Server 2010, with “contoso\administrator” granted administrator permissions.

SharePoint Server 2010 has been configured in a “Complete” farm using Kerberos authentication and the default SQL Server 2008 instance for data, and has a site collection created using the Team Site template at http://intranet.contoso.com/ and a FAST Search Center at http://intranet.contoso.com/search/.

In order to run this demo you will need the following:

• Windows Server 2008 R2 with the Hyper-V role enabled.
• Drive Formatting: NTFS
• Processor: Intel VT or AMD-V capable
• RAM: 8 GB or more recommended
• Hard disk space required for install: 50 GB

http://www.microsoft.com/downloads/details.aspx?FamilyID=0c51819b-3d40-435c-a103-a5481fe0a0d2&displaylang=en