Force Rebuild of the Project Server Reporting Database

Background

The Microsoft Office Project Server 2007 Reporting database can become corrupt at times causing general queue job failures when publishing projects when invoking the Reporting message processor throwing exceptions that cite FOREIGN KEY constraint conflicts. Sometimes these are spurious and random in nature, and you can correct them simply by forcing a rebuild of the Project Server 2007 Reporting database.

Resolution

To force a rebuild of the Project Server 2007 Reporting Database, follow these steps:

1. Logon to Project Web Access with Administrator credentials
2. Select Administrative Backup from the Database Administration section on the Server Settings Page in Project Web Access
3. In the Items for Backup section of the Backup page, select the checkbox for Enterprise Custom Fields and then click the Backup button and click the OK button when prompted by the system
4. Select Administrative Restore from the Database Administration section on the Server Settings Page in Project Web Access
5. Choose Enterprise Custom Fields from the Choose Item selector on the Restore page
6. Click the Restore button and then click the OK button when prompted by the system

Allow time for the reporting rebuild job to run. You can track the state of this job on the Manage Queue page.

 

Discontinued features and modified functionality in Microsoft Project Server 2010

Applies to: Microsoft Project Server 2010

 

If you are familiar with previous versions of Microsoft Project Server, the following sections describe features and functionality that have been discontinued or changed in Microsoft Project Server 2010.

Project Portfolio Server changes

Project Server and Project Portfolio Server are no longer two separate products. Relevant portfolio functionality from Project Portfolio Server has been merged into Project Server 2010. The following Project Portfolio Server 2007 features and functionality were discontinued or changed for Project Server 2010:

• Application portfolio management   This includes tracking and managing applications.
• Audit Trail   Workflow activity was previously made available from the Audit Trail link in the Workflow module. In Project Server 2010, this information is available in the Workflow History list, which can be accessed from the Additional Workflow Data link in the All Workflow Stages section.
• Benefits estimating   This includes estimating and tracking financial and non-financial benefits.
• Organizational hierarchy and aggregates   This includes a security-based hierarchical data grouping and aggregation. In Project Server 2010, departments have been added to enable hierarchical data grouping based on organizational structure.
• Dynamic charting   This includes the Chart Wizard, which allows for ad-hoc interactive chart creation, including bubble chart modeling. In Project Server 2010, Excel Services support has been added, providing a new method of dynamic reporting.
• Financial management   This includes time-phased budget, actual, and forecast cost tracking. In Project Server 2010, use custom fields and Excel Services to enable cost functionality for simple estimation, tracking, and forecasting costs. Solutions for more complex estimating, tracking, and forecasting costs are offered by Microsoft partners.
• Insight analysis   This enabled users to get specific details into the factors that impact a specific portfolio selection.
• Decision dashboard   This enabled users to make selection decisions supported by a rich dashboard with live grouping and charting.
• Sensitivity analysis   This enabled users to take a portfolio selection through various what-if scenarios and figure out how close a project was to being selected.
• Snapshotting and versioning   This enabled users to create cost, resource, and benefit snapshots at any given point in time. In Project Server 2010, reporting and base-lining can be used to capture data snapshots.
• Surveys   This includes flexible, user-definable survey forms, on subjects related to risk, architectural fit, and operational performance.

 

Other changes

In addition to the portfolio functionality changes, the following list describes other changes implemented in Project Server 2010.

• Outlook add-in    The Outlook add-in for Project Server has been discontinued in Project Server 2010. The existing add-in can still connect to Project Server 2010, however it has not been updated for this release. Instead, Project Server 2010is integrated with Exchange Server, so that users no longer need to download a separate COM add-in. The timesheet functionality that was present in the Outlook add-in has been discontinued.
• Activity plans and personal projects    included the ability to create and manage activity plans, also known as lightweight projects, and personal projects from within Project Web Access. Instead, Project Server 2010 supports editing any project on the server using a rich, new grid control in Project Web App.
• Color indicators on the My Tasks page   Color indicators on the My Tasks page have been replaced with the text from the tool tip for the indicator, paired with a background color for the text.
• Data analysis    The underlying technology used for data analysis in previous versions, Office Web Components, has been discontinued. In Project Server 2010, this technology has been replaced with Excel Services.

PerformancePoint Integration with SharePoint

SharePoint 2010 EE & PerformancePoint Server

Creating Scorecard - PerformancePoint Server 2007

PerformancePoint Server Demo