M
Michael
I have completed the MS Project 2003 Starter Solution to extend the
OLAP cubes for Task Risks and Issues, but had a question about
separating updates for tasks risks\issues from that of the standard
Portfolio Analyzer (PA) updates for Resources. As it stands now, when
I go to Manage Enterprise Features in Project Web Access (PWA), the PA
Resources are updated and the MSPOLAPBREAKOUT.dll is called to drop the
Risk and Issues staging tables, recreate them, repopulate them, drop
the OLAP cubes for Risks and Issues, and finally build new cubes for
Risks and Issues based on the new staging table data.
Is there a way to separate these updates so that PA runs its own
updates at interval A and the Risks and Issues updates run at interval
B? My guess is the answer is No simply because they run in the same
Analysis Services DB, but wanted to make sure.
OLAP cubes for Task Risks and Issues, but had a question about
separating updates for tasks risks\issues from that of the standard
Portfolio Analyzer (PA) updates for Resources. As it stands now, when
I go to Manage Enterprise Features in Project Web Access (PWA), the PA
Resources are updated and the MSPOLAPBREAKOUT.dll is called to drop the
Risk and Issues staging tables, recreate them, repopulate them, drop
the OLAP cubes for Risks and Issues, and finally build new cubes for
Risks and Issues based on the new staging table data.
Is there a way to separate these updates so that PA runs its own
updates at interval A and the Risks and Issues updates run at interval
B? My guess is the answer is No simply because they run in the same
Analysis Services DB, but wanted to make sure.