Project Server 2007: Rebuild Reporting database

A

Adrian Miller

Hi,

our Reporting Database shows old projects which had been deleted long time
ago. How do I reintialize the reporting Reporting Database?

Thanks in advance for any hint
Adrian
 
P

Paul Conroy

I asked Brian Smith (MSFT EPM Support God) the same question. This was his
response.

One technique we use if the support incident doesn’t require a complete
reporting DB is to restore the customer’s draft and published, then use an
archive and reporting database from a provisioned site that has not been used
(so “empty†but complete with schema – tables, views, static stuff). You
then need to set the site collection guid on the archive and reporting to
match the draft/published and finally provision a site. Restoring DB’s over
existing DBs will always give problems as GUID references will not be right.

We tend only to use this as a time saver if the archive and/or reporting are
very large and it saves time restoring. It isn’t something we use for
customers to get a clean reporting DB as the timesheet data cannot be
recovered.

The reporitng DB will then rebuild to some extent – all EPM stuff will be
OK, and also WSS once published – but you will never get back the timesheet
data. For some support scenarios this doesn’t matter.

--
If this post helped you, consider passing on the good will by making a
donation this childrens charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.co.nz
 
M

Mike Mahoney

I asked BrianSmith(MSFT EPM Support God) the same question. This was his
response.

One technique we use if the support incident doesn't require a complete
reporting DB is to restore the customer's draft and published, then use anarchiveand reporting database from a provisioned site that has not been used
(so "empty" but complete with schema - tables, views, static stuff). You
then need to set the site collection guid on thearchiveand reporting to
match the draft/published and finally provision a site. Restoring DB's over
existing DBs will always give problems as GUID references will not be right.

We tend only to use this as a time saver if thearchiveand/or reporting are
very large and it saves time restoring. It isn't something we use for
customers to get a clean reporting DB as the timesheet data cannot be
recovered.

The reporitng DB will then rebuild to some extent - all EPM stuff will be
OK, and also WSS once published - but you will never get back the timesheet
data. For some support scenarios this doesn't matter.

--
If this post helped you, consider passing on the good will by making a
donation this childrens charity.http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.co.nz







- Show quoted text -
Click to expand...

Paul

Which table contains the site collection guid?

thanks

Mike
 
Top