Featured Case Study:

 

By the time Skylight Financial, Inc. began an in-house implementation of SharePoint, inefficient work flows and scattered communication processes had already become a source of major frustration.

 

Read More >
SharePoint Tip of the Month:

Enter your email below to receive our SharePoint Tip of the Month:

This month’s tip >

SharePoint Tip of the Month

October 2009: How The SharePoint 2010 Architecture Will Change The Way Businesses Look At SharePoint

 

The architecture of SharePoint 2010 fundamentally changes the way organizations will think about the platform.

 

  • Smaller companies that have heretofore been limited to vanilla SharePoint hosting offerings will now be able to deploy customized solutions on a shared hosting platform.

  • Large organizations that deploy a SharePoint server farm for shared services use by their employee base will no longer have to so tightly constrain their internal customers' use of the product because of governance issues.

  • And third party providers will now have a vehicle for delivery of their value added features, functions and applications to the mass market via hosted services.

 

How will this all be possible? Following are some specific examples of what the new architecture offers:

 

  • Multi-Tenancy and Distributed Services – For large enterprises who host SharePoint farms and distribute ownership of sites to administrators throughout the corporation, there is now the notion of tenancy. Each individual tenant will be able to pick and choose from among the services – i.e., Excel Services, Forms Services, User Profiles, etc. – that they wish to consume. Using this model, the services will consume fewer overall system resources than under the old model. Additionally, it will create the opportunity to define charge-back structures that fairly distribute infrastructure costs to those consuming the services.

  • Stress Management – Under SharePoint 2007, quotas could be assigned to site collections for total disk space usage, but nothing else. With SharePoint 2010, a certain number of total “resource points” will be allotted to each tenant or site. The points are spent based on a number of server metrics, including memory consumption, SQL Query time, non-responsive processes, CPU execution time, and others. When an individual has consumed its daily quota of resource points, it will become unavailable without bringing down the other sites. Additionally, large list throttling will enforce limits on the amount of stress that lists with too many records can place on the overall server. Whereas the previous version of SharePoint only provided guidance on the number of items to keep in a list or view, the new version will minimize the impact of failing to adhere to this guidance.

  • Sandbox Solutions – Sandbox solutions are pieces of code that can be made available to individual sites. In all previous versions of SharePoint, custom solutions were installed at the farm level. Farm administrators were often reluctant to allow custom coded solutions without long, detailed testing cycles, if they were willing to allow them at all. Sandbox solutions will mean that site owners can have local code that is only visible in their sites and can only impact performance locally. This will mean substantially less risk to server administrators in allowing custom code, which will mean wider availability and a reduced time to market for custom solutions.

  • Improved Monitoring – Usage and health reports will provide system administrators with the ability to proactively identify problem areas and respond to them before they are noticed by end users. Additionally, better logging will make it easier to troubleshoot problem areas and error messages.

  • Search Performance – An entire SharePoint Tip could be dedicated to what is coming with the search enhancements. With respect to large scale deployments of SharePoint, 2010 will now scale to 2 billion items per content index, 200 times that amount from the SharePoint 2007 platform.

  • Vanity URLs – In SharePoint 2007, custom web addresses (i.e. "http://www.yournameinlights.com") were assigned at the web application level. This effectively meant a small limit – around 20 – on the number that could be hosted on a single web server. In 2010, they can be assigned to site collections, which means custom URLs can be distributed to a much wider audience.

 

The bottom line here is that SharePoint 2010 is going to be a game changer for many who previously found the platform to be either out of reach, limited, or impractical.

 

More Tips...

 

02/10: Monitoring User Activity with SharePoint Usage and Audit Reports

 

01/10: Planning For Your Upgrade to SharePoint 2010

 

12/09: Unlocking the Code For True, Cost-Effective SharePoint Workflow

 

11/09: Bringing Products to Market More Efficiently with SharePoint

 

10/09: How The SharePoint 2010 Architecture Will Change The Way Businesses Look At SharePoint

 

09/09: Using SharePoint to automatically trigger periodic document review

 

08/09: Getting Ready for SharePoint 2010

 

07/09: SharePoint 2010 Sneak Peek and Kevin’s First Thoughts

 

06/09: Leveraging Your SharePoint Investment for Business Productivity

 

05/09: Performance Point Server's Place Within the Business Intelligence Product Stack

 

04/09: Implementing a SharePoint Learning Management System

 

03/09: SharePoint Based ISO 9001 Document Management System

 

02/09: Implementing a SharePoint Knowledge Base

 

01/09: Planning For Your SharePoint Portal Deployment

 

12/08: Creating a Dashboard Using Excel Services

 

10/08: Six Sigma Based Project Portfolio Management Using SharePoint

 

09/08: Using SharePoint to Achieve Advanced Knowledge Management for the Enterprise

 

08/08: Remote SharePoint Acceleration for Improved Productivity

 

07/08: Top 10 Things to Think About When Implementing Your SharePoint Governance Plan

 

06/08: Using SharePoint to Measure Performance

 

05/08: Automatically Converting Reports To PDF in SharePoint

 

04/08: Managing the Pain of SharePoint Document Migration

 

03/08: SharePoint as an ECM Solution

 

02/08: Automating the Site Provisioning Process

 

01/08: Getting The Most out of Enterprise Search

 

12/07: Making Sense of SharePoint's Workflow History

 

11/07: Realizing the Value of Your Intellectual Assets with SharePoint Knowledge Management

 

10/07: Full Featured Business Applications Using SharePoint 2007

 

09/07: Web Content Management Breakdown

 

08/07: Using SharePoint 2007 Content Types

 

06/07: Approaches to SharePoint Branding and Design Customizations

 

05/07: Streamlining Report Approvals using SharePoint and InfoPath

 

04/07: Content Rollup

 

03/07: Information Management Policies and Records Retention

 

02/07: Building an Enterprise-Wide Staff Directory

 

01/07: Using SharePoint, InfoPath Forms and Workflow to Automate Your Employee Onboarding Process

 

12/06: Extranet Authentication Options

 

11/06: Planning for Your Migration to Microsoft Office SharePoint Server 2007

 

10/06: Business Intelligence Capabilities in SharePoint 2007

 

09/06: Understanding Workflow Capabilities in SharePoint 2007

 

08/06: Fulfilling the Promise of Your SharePoint Portal - A Whitepaper by Abel Solutions

 

07/06: New Features in SharePoint 2007 - Part II

 

06/06: Several New Features in SharePoint 2007

 

Sign In