share point 2007 versus 2010 comparison

8/2/2019 Share Point 2007 Versus 2010 Comparison

1/18

SHAREPOINT 2007 Vs. 2010Comparison between SharePoint 2007 and 2010

3/12/2012


2/18

ContentsSHAREPOINT 2007 VERSUS 2010 COMPARISON .......................................................................................... 2

User Interface Changes ............................................................................................................................. 2

List Changes .............................................................................................................................................. 3

Content Management Changes ................................................................................................................ 4

Software Development Changes .............................................................................................................. 6

Functional Changes ................................................................................................................................... 7

Backup/Recover/Upgrade Changes .......................................................................................................... 8

Web Services Changes .............................................................................................................................. 8

Site Changes ............................................................................................................................................ 13

Search Changes ....................................................................................................................................... 15

Database Changes ................................................................................................................................... 16

Architecture Changes .............................................................................................................................. 16

New Databases ....................................................................................................................................... 16

SharePoint Configuration Database Changes ......................................................................................... 17


3/18

SHAREPOINT 2007 VERSUS 2010 COMPARISONSharePoint went through a major overhaul in capability, ease of use, ease of administration, and ease of

integration. This comparison of SharePoint 2010 versus SharePoint 2007 is for those most familiar with

the 2007 version.

User Interface ChangesCustomers familiar with the previous version of SharePoint will notice some major changes to the user

interface in SharePoint 2010.

The new changes are:

Ribbon UI all managements and changes are done via the new Ribbon UI interface that weknow by Office 2007 that is called Fluent UI now. This user interface concept has been adopted

by SharePoint 2010 to provide a seamless, familiar and responsive user experience across the

entire Office suite

Multilingual UI SharePoint 2010 provides different localization of the interfaces. Comparing toSharePoint 2007 when you can localize only content, SharePoint 2010 provides you multilingual

support for Ribbon, menus and site navigation. Moreover, site owners can configure fields

within lists to support multiple languages.

Compliance and Accessibility app pages are XHTML, WCAG 2.0 AA complaint. Unfortunately,SharePoint still categorize browsers on two levels. - Level 1 and 2 browser support. Level 1

browsers are: IE7, IE8, FF all 32bit browsers where 100% of functionality is guarantee; Level 2

browsers are IE7-IE8 x64, Safari, FF on other platforms, with some limitations in rendering and

behavior. IE6 is not supported


4/18

Validation of List and Libraries each item in a list or library now supports item-level and list-level validation. For instance, a list owner can configure a validation to disallow the start date of

an event item, stored in one column, to be after the end date of the event, stored in another

column

Office Web Services - SharePoint 2010 features rich out of the box integration with Webversions of the most popular Office client applications so people can access documents,

spreadsheets, presentations and notes without worrying the machine they are on has the latest

Office client installed

Old Look and Feel - the standard 2007 theme is supported, and is default when you performmigration from SharePoint 2007

[new] Themes no longer exist in Windows SharePoint Services "14" and Microsoft SharePointServer 2010, so any customizations and design work that you have done with themes will not be

imported into the new interface

[new] Two way of UI changes customization of UX or simple via API that become possible withSharePoint 2010

[new] Office Web Services is a replacement for the Office client and installing on the top ofSharePoint 2010 to provide all functionality of the Office 2010 over the Web, thus allowing users

to collaborate and edit documents interactively together.

[new] 10 New and 4 removed Templates - the following templates have been added toSharePoint 2010: GroupBoard, Visio Process, Bugs, Charitable Contributions, Projects, Enterprise

Search Center, Basic Search Center, FAST Search Center, Enterprise Wiki . The next ones have

been removed: Site Directory, Search Center with Tabs, Search Center, Collaboration Portal

[new]Validation of the users input into list columns (formula based) [new] Configuration Wizards in Central Administration simplify the most popular command

actions, for example Farm Configuration Wizard

List Changes

SharePoint 2010 introduces the following changes to the List:

List items now display in a screen overlay pop-up. New events - WebAdding, WebProvisioning, ListAdding, ListAdded, ListDeleting, ListDeleted Site Collection events Synchronous "after" events to perform post-processing Custom error pages New property PSEventPropertiesBase to store the user name and token of the person who

triggered the effective action

New integrity constraints based on the lookup Projected Fields - fields from the parent which are referenced and displayed in the child list Lists Join - via LINQ, CAML, SharePoint Designer and API (SPQuery.Join and

SPQuery.ProjectedFileds)

Max 50M items under the read scenario


5/18

List query size threshold - return warning or exception of query result exceeds threshold numberof records

Threshold pre-set is 5000 items for the normal user and 20000 items for the Super User List Administrators are notified when lists exceed threshold List constraints - max 8kb of data per list item (excluding attachments), 6 projected fields on

joins (except using the view fields)

Columns can be flagged as UNIQUE (must be indexed) Columns can be validated using custom field or by other fields

Content Management Changes

SharePoint 2010 contains a robust list of rich features that brings ECM to more people within an

organization. Most notably is the fact that many records management capabilities in the previous

version of SharePoint that were locked to specific site templates are now encapsulated in Features

enabling their use in any SharePoint site.

Managed Metadata The ability to centrally define taxonomies that can be leveraged withinand across farms to classify and find content quickly.

Unique Document IDs The ability to assign a document a unique identification number peoplecan use to retrieve the document later even if it is moved

Document Sets The capability to group multiple work items into one consolidated atomicwork product. Document Set share the same metadata and the entire Document Set can be

versioned as a whole and downloaded as a compressed ZIP file with all the contents. Each

Document Set has a Welcome Page which displays the metadata shared across all documents in

the set as well as a list of all documents. People can customize the Document Set Welcome Page

as any other Web Part Page to meet the current business requirements

Advanced Routing The ability people to submit documents to SharePoint sites and let thesystem determine which library and/or folder it should be saved to using the document's

metadata and other rules.


6/18

In-Place Records Management The capability that enables a document to be flagged as anofficial file or record, thus prohibiting any future changes, within collaboration sites. These

official records can reside within the same document libraries that contain other documents

people are collaborating on.

Web Content Management The capability to host a content-centric site consumable by peoplewith minimal or no collaboration complete with a robust publishing workflow ensuring only the

privileged people have permissions to add and edit content on the site.

Searching by metadata tags - for content based on metadata breaks down the boundaries offolders, lists and document libraries, sites and site collections.

Metadata is extracted from images - metadata is by automatically extracting and promotingmetadata from images uploaded to the central Asset Library. This includes details such as EXIF

data and other details stored with images. This metadata can be used by people in search

queries or when browsing the Asset Library using specific criteria

Auto Metadata Tagging - folders within lists and libraries can be configured to automatically tagcontent with specific metadata such as adding a "year=2010" tag to all documents within the

"2010" folder.

Content Rating - people vote for which content is more helpful than others. SharePoint 2010includes a content rating capability that can be leveraged in search queries or custom search

solutions to find the most popular content as defined by the people in the organization

Content Organizer feature you can define a set of rules and have SharePoint route thedocuments automatically (like it happened for records management, but now for all

documents).

Content types sharing content types can be shared across sites, web applications and farms External Content is supported via External List of SharePoint 2010 and External Columns (you

can use existing list + attach the external content) Social data in User Profiles - In Microsoft SharePoint Server 2010, user profile service facilitates

a user applying social data on a URI. This is happening via Web services protocol [MS-UPSSDSP]

that attaches social metadata to the corresponding URI. A user can select, for example, a

document or an arbitrary URL and attach additional social metadata to the URL. Some common

scenarios for using metadata include:

o The ability to rate a document or content or persono Add a note or comment to contento The ability to bookmark content with some pre-defined keywords, such as a favoriteo Add tags to the content, to categorize content or highlight with colleagues In case of

bookmarks and tags, user profile service works with the Content Management Serviceto store the value of the tag, and the user profile service database only stores the

corresponding GUID.

o For all forms of metadata, four key pieces of information are stored in the user profileservice database

who added the metadata that is the record identifier of the user in the profile store when was it added that is a timestamp


7/18


8/18

Microsoft SharePoint Server 2010 contains more than 1,500 deprecated types , most in theMicrosoft.SharePoint.Portal

User Code Execution Service - Microsoft SharePoint Server 2010 implements a capability tosecurely host custom solutions and executable code that comes from customers of the system.

It provides better controls for the security of execution of custom code, as well as mechanisms

to monitor and control the usage of resources by that code.

One requirement of these mechanisms is to move the execution of the code to separateprocesses and separate servers, to provide better layers of isolation and monitoring. Therefore,

two roles are defined in a user code execution process: a front-end Web server which initiates

requests to run user code on behalf of a user, and a code execution back end service which

fulfills the execution request. Communication between these servers is specified via the User

Code Execution Protocol specification ([MS-SPPTC]).

Three object models - Managed .NET API, Silverlight Object Model, JavaScript & ECMAScriptlibrary

Functional Changes No SSP the new model of Serviced Applications replace the deprecate SSP in SharePoint 2010.

The Service application architecture allows a set of services to be associated with a given Web

application and a different set of services to be associated with another Web application (By

publishing a service application, it can be shared across server farms)

The BCS is actually a platform that provides a SharePoint-based framework for creating OfficeBusiness Applications, or OBAs. BDC Entities became external content type (ECT) . Business

data can be exposed as Office Word document properties and can be inserted into documents.

Users can interact with business data using the familiar Outlook interface, and take the data

offline using the new SharePoint Workspace

Claims based Identity, a system to describe, trust, and act on the identity of users accessingSharePoint. It is a capability that exists in addition to Windows based Authentication

(NTLM/Kerberos). SharePoint Server 2010 Technical Preview implementation of Claims based

Identity is standards based. Customers deploying SharePoint Server 2010 Technical Preview, can

use any protocol or service that implements these standards to provide Identity to SharePoint.

In addition, when applications running on SharePoint need to make external Web service calls,

SharePoint will issue a SAML token that identifies the user and application pool identity. For

more information on Claims based Identity standards, see [WSTrust], [WS-Security],

[WSFederation] and [SAMLToken1.1]

Composition Application that allows connecting to external data using SharePoint Designer2010 to create an external content type. This external data can now be leveraged within the

Office clients such as Word or Excel. Custom task panes in Outlook can use this data from

external line-of-business applications to augment a person's contact card when selected such as

their company's recent orders, etc.

User profile service export data back to Active Directory and Lightweight Directory AccessProtocol (LDAP). In Microsoft SharePoint Server 2010, a user profile service administrator can


9/18

define properties that will be exported back to the Active Directory. A popular scenario for the

export functionality is to send a users picture back to be stored in Active Directory

Visio 2010 - you can create workflows in Visio 2010 and export them into SharePoint Designer2010 to add business logic and additional rules

Internal SharePoint DesignerBackup/Recover/Upgrade Changes

New upgrade scenarios - SharePoint Server 2010 has several features that have beenintroduced that allow for upgrade scenarios to occur with little to no outages and at the same

time allow for quicker upgrade windows.

The first feature is the use of read-only databases which was made available starting with OfficeSharePoint Server 2007 service pack 2. SharePoint Server 2010 now recognizes a content

database has been made read-only from with-in SQL Server and will trim the UI as if all site

collections were marked read-only. This allows users read access to the content while the

upgrade takes place.

Patching improvements. The patch management UI and patch reporting cmdlet allow for themonitoring of patches throughout the farm. There are also patch status health rules that will

alert an administrator to inconsistencies

Granular Backup/Restore from Central Administration (not only via STSADM) includingrecovery single document

Recover data from unattached content database - you don't need to attach content databasebackup to the SQL Server to recover data from there

Browse the content of a content database that is attached to a SQL server but not associatedwith SharePoint Server

Automatic Failover Workflows are not Imported/Exported - when you export/import your Site Workflows won't be

included, you need to move them manually

Web Services Changes

SharePoint 2007 Web Services model provided limited functionality to manage SharePoint farm over the

web model. The reason of this is that SharePoint 2007 was considered as a stand-alone product, without

Web 2.0 features and Cloud services. In nowadays, we are moving to online services and rich Web

Services model is one of the requirements for all products we are using, especially for enterprise wide

applications that can be scaled globally.

The release of SharePoint 2010 takes into account Web 2.0 and Cloud trend and exposes all new

functionality that is exposed not only via SharePoint API, but via Web Services, WCF model and JSON

protocol.

Microsoft direction is to provide you rich web API to expose all stand-alone power of SharePoint over

the wire.


10/18

SharePoint 2010 Web Services were refactored completely to incorporate all power and flexibility of

WCF 4.0 technology. New functionality is provided via Web Service mode, as WCF services and supports

JSON protocol for Web 2.0 integration

All services are exposed over the same URL patterns:

- Administrative services: http://: /_vti_adm/Admin.asmx

- Site services: http://: / /_vti_bin/ .asmx

However, all new MSS2010 functionality (services) are exposed over additional Web Services, that have

new URLS like: http://: / /Admin.asmx

Changes in existing Web Services

There are few services that were updated to provide additional method.

Lists

The list services provides functionality to work with the List libraries

Sites


11/18

The "Sites Web Service provides new methods to manage SharePoint sites (workspaces). Previously, in

SharePoint 2007 you can't create workspaces for the root site via Web Services. But now, SharePoint

2010 extends Web Service model and provides methods to manage Workspaces.

With the new method you can get the Web Application ID, create SharePoint Workspace, export site

schema as deployable cab file and delete the Workspace, for example use the following snippet to

create new ws2010changes Team Site beneath the current site with the anonymous access.

siteService.CreateWeb("ws2010changes", "WS2010Changes", "MSS2010 Web Services changes

samples", "STS#0", 1033, true, true, true);

CreateWeb method has the following signature (from autogenerated WS classes)

object[] results = this.Invoke("CreateWeb", new object[] { url, title,description, templateName,

language, uniquePermissions, anonymous, presence});

Site Data

Webs


12/18

Form Services

Excel Services


13/18

Official File

Search

User Profile Services


14/18

Web Part Pages

Site Changes

SharePoint 2010 Site Changes

Role/Rule based Audience Targeting added rules-based audiences, WSS groups anddistribution list membership.

Sites are collection of pages - SharePoint 2010 sites became more page-focused rather than acollection a lists. Sites still contain the same list and libraries as previous versions of SharePoint,

but the site is now a collection of pages.

Pages are optimized for Reading all WCM pages are optimized for the reading, rather than forthe writing, thus performance is increased significantly

Status updates and activity feeds of My Sites SharePoint 2010 changes of My Site enhanceddramatically to be the social networking hub. One of such changes is ability to update your

status, similar to Facebook. See the following screenshot


15/18

Social tagging - assignment of descriptor words or categories to that content. There are twotypes of tagging, social tagging and expertise tagging. Social tagging refers to content and adds

metadata to content to describe what it is, what it contains, or what it does. Expertise tagging is

related to a person and describes the person, such as what they do, which projects they work on

or what skills they have. Where social tagging of content allows users to organically flex and

grow a portals information architecture over time, expertise tagging helps build relationships

and connections to other people in the organization.

Team blogs which allows multiple people to publish blog posts together New Lists - Assets Library (list to share and manage rich media assets such as image, audio and

video files) , External List (list whose data source is an Enterprise Entity)

Site templates are deprecated in SP2010. But, "Save Site as Template" will create a solutionpackage with a .wsp file name extension

[new] Improved performance and management of large lists. List item limitation has beenremoved 1 million items for 3secs. Windows SharePoint Services "14" and Microsoft

SharePoint Server 2010 apply a default query threshold of 5,000 items. Any custom code that

relies on query result sets that can exceed this maximum will not behave as expected. Queries

on lists consisting of more than 5,000 items that include non-indexed fields in their query

conditions will also fail, because those queries must scan all rows in a list. You can increase this

limit or enable the object model to override it on the Central Administration site (under


16/18

Application Management, click Manage Web Applications, click General Settings, and then click

Resource Throttling

Lists support external data, can return results as Dateable; support calculated field rulevalidation and no more event receivers

Search Changes Three ranges of search Search Server 2010 (Entry Level), OOTB Search, (Infrastructure), and

FAST Search (high-end). FAST will be licensed through our Enterprise CAL (for internal search)

with an additional server

No more 50 million items limitation - FAST provides powerful capabilities to index hundredmillions items, so no more SharePoint 2007 index limitations

Query syntax can use AND, OR, NOT keywords in search query Wildcard search - using * in search query Faceted search/Refinements refinements are shown in the panel to filter the results (by tags

and metadata). This functionality is supported in the Standard edition and above

New search Web Parts - many search-related Web Parts that enable power users to createcustomized search experiences that implement automatic filtering, best bets, a refinement

panel, featured content or offer pre-defined queries

Social people search - phonetic name matching (returns names that sound similar to what theuser has typed as a query & all variations of common names, including nicknames); exploring

results via name, title, and expertise; include real-time presence through Office Communication

Server

Social distance - SharePoint builds a model of your regular interactions based on e-mailconversations and group memberships, which it uses to organize people search results based on

social distance - a direct colleague will appear before someone 3 degrees removed.

Index Partitioning - SharePoint Search supports partitioning the index and having multipleindexers that can be aggregated together

Query Partitioning - Each query partition can contain up to ~10 million items, and can also becloned by deploying multiple instances of a given query partition across several query servers.

Query throughput increases when you add query partition instances.

FAST Search replacement - The new architecture scales up to approximately 500 million items,and search can be utilized in a multi-tenant hosting environment.

Crawling Service - Multiple crawlers can be used simultaneously to crawl different contentduring each crawl cycle. This improves performance and can also provide redundancy. All

crawling information is stored into property database. Cross-farm search service that allows farms to connect to multiple farms to consume cross-farm

data

Metadata index is expose via search Search Server doesn't support people search - this functionality is available only in SharePoint

2010 OOTB Search


17/18

FAST Search services in 2010 means that ingesting structured data from external Line ofBusiness applications is much easier in FAST Search for SharePoint.

Database Changes

SharePoint 2010 database model has been changed significantly in the way of distributing data across

several databases that makes horizontal distribution of SharePoint 2010 solutions very feasible.

There are three areas of changes - architecture changes, new databases and new tables.

Architecture Changes

SharePoint 2007 stored all content in large tables (for example lists, site collects end etc. were

represented as a huge table), and the performance were affected by SQL Server locks, especially in the

large collaborative projects, when a lot of people use the same content and SQL Server locked the table,

so no one can work till person generated the lock release the content (SQL Server 2005 suffered from

this very much, because its internal behavior tends to lock table when 2000+ items are selected).

Thus, you were limited with 2000 items in List and should use several Site Collections in case of large

collaborative community.

SharePoint 2010 changes solved those issues - moving content from the singe tables into different

tables. Such changes allow you to store million items in the lists and have very intensive collaborative

project in one Site Collection.

100 GB "recommendation" on the Content Database size is not an issue any longer.

New Databases

SharePoint Shared Services became deprecated in SharePoint 2010, and instead we have new Services

architecture, where all services are independent from each other. Such architecture affected the way

information and configurations are stored and each service has its own database.

Previously, with SharePoint 2007 we had at least 6 databases for each installation

1. Central Administration - [SharePoint_AdminContent ]2. Configuration - [SharePoint_Config]3. SSP - 3 databases for

I. SSP settings,II. My Sites,

III. Search4. Web Application - custom databaseWith SharePoint 2010 model we still have Central Administration and other databases, but instead of

point 3 we end up with the separate database for each Service, for example [AccessServices],

[MetadataServices], [WebAnalyticsReporting] and etc. So, we can easily have 15 databases only for the

simple SharePoint 2010 solution.


18/18

[new] User Profiles uses 3 databases:

I. [Profiles] - for the actual profile content,II. [Synchronization] to keep configurations of the external data

III. [Social Tagging] to store tags and noted created by usersSharePoint Configuration Database Changes

There are several changes of the tables in the SharePoint Configuration database. The following tables

have been added:

AllFileFragments AllListAux AllListPlus AllListUniqueFields AllLookupRelationships AllWebParts (Renamed from WebParts) CustomActions Resources SharedAccessRequest SiteDeletion SolutionResourceUsageDaily SolutionResourceUsageDailyOriginal SolutionResourceUsageLog SolutionResourceUsageLogWindowed Solutions WebsPlus

Removed Tables:

Categories Image0x WebCat

share point 2007 versus 2010 comparison

Documents