Hi all,
At last the SP is available.
For more information about what's available in SP2, please check the online help:
Office Online: http://office.microsoft.com/en-us/performancepoint/FX102380591033.aspx
Overview of specific enhancements in Service Pack 2:
Addition/Change | Important Information |
SQL Server 2008
support now included in PerformancePoint Server 2007, SP2. | Please
install SQL Server 2005 SP2 before installing SQL Server 2008. |
The Show Details action is now available for PerformancePoint Server reports using data stored in SQL Server 2008 Analysis Services. | Show Details provides quick access to details for dashboard consumer: simply right-click in a cell or on a chart value to see the transaction-level details |
PerformancePoint Server 2007 with SP2 now supports Windows Server 2008 Hyper-V. | Hyper-V creates new opportunities for server virtualization. You can use Hyper-V to make more efficient use of system hardware and host operating system resources to reduce the overhead associated with virtualization.
For more information, see the PerformancePoint Server 2007 Hyper-V guide. |
Use PerformancePoint Server Dashboard Designer on computers running .NET Framework 3.5 alongside .NET Framework 2.0. | Please install .NET Framework 2.0 before installing .NET Framework 3.5. |
You can now use PerformancePoint Server with domains that have apostrophes in their names | Provides more domain name flexibility.
In previous versions of PerformancePoint Server, when a domain name included an apostrophe, the configuration tool failed for both Planning Server and Monitoring Server. |
Scorecard key performance indicator (KPI) queries are improved. | Timeout errors no longer occur with scorecard key performance indicators (KPIs) using data stored in SQL Server 2005 Analysis Services. |
Improvements to Time Intelligence filters, including enhancements to calendar controls and scorecard KPI's using data stored in analysis services. | Prior to SP2, the calendar control for Time Intelligence Post Formula filters sometimes displayed 31 days for each month. Additionally, some Time Intelligence expressions caused filters that were linked to KPIs to fail. For example, when a compound expression such as (Day-7:Day-1) was used in a Time Intelligence Post Formula filter and that filter was linked to a KPI, an error message occurred. |
Ronen