Approaches to migrating your service applications

While working my way through TechNet documentation, I came across this very interesting table! It describes supported methods for service application migration.

The forth column shows the support for read-only database. You can find more information on read-only databases here: Run a farm that uses read-only databases (SharePoint Server 2010) [http://technet.microsoft.com/en-us/library/dd793608.aspx].

Service application

Database

Supported approach

Supports read-only

Notes

Access Services

None

not available

not available

 

Application Discovery and Load Balancing

None

not available

not available

Application Registry Service

Application Registry Service

Recreate

No

Business Data Connectivity

Business Data Connectivity

· Database attach

· Recreate

Excel Services

none

not available

not available

Microsoft SharePoint Foundation Subscription Settings

Subscription

Database attach

Managed Metadata Service

Managed Metadata Service

· Database attach

· Recreate

PerformancePoint Services

PerformancePoint Services

Recreate

PowerPoint Service

None

not available

not available

Project Server service application

· Draft

· Published

· Archive

· Reporting

Database attach

No

· Requires synchronization between the databases

· Need to configure time stamps or log marking

For more information, see Database-attach full upgrade to Project Server 2010

SharePoint Server Search

· Search Administration

· Crawl

· Property

· Recreate

· SharePoint backup and restore

No

· The index partitions are copied to the new farm and then restored on the new database server.

· The search topology is exported and then restored to the new server.

Secure Store

Secure Store

· Database attach

· Recreate

The pass phrase for the new database must be identical to the source database.

Security Token Service

Recreate

State Service

State

Recreate

No

Usage and Health Data Collection

Logging

Recreate

No

User Profile

· Profile

· Synchronization

· Social tagging

· Database attach

· Recreate

Profile requires the restoration of an encrypted FIM key

Visio Graphics Service

None

not available

not available

Web Analytics Service

· Staging

· Reporting

· Database attach

· Recreate

Word Automation Service

Word Automation Services

Recreate

not available

Word Viewing Service

None

not available

not available

 
Advertisements

Display exceptions in application pages

SharePoint OOTB displays user friendly an error page to end users. As a developer we want the .NET error page displaying detailed information about the exception thrown. By updating the web.config file with the following parameters the detailed information is displayed.

<configuration> <SharePoint> <SafeMode CallStack="true" /> </SharePoint> <system.web> <customErrors mode="Off" /> <compilation debug="true" /> </system.web> </configuration>

By only changing the web.config file in the web application root, located in “C:\inetpub\wwwRoot\wss\<webapp>”, will not display detailed information in application pages (a.k.a. layouts pages).

There is more than one web.config file! Check your SharePoint Root folder.

Update the configuration show above in the “…\14\TEMPLATE\LAYOUTS\web.config” file and this will result in a .NET error page for application pages.