Project Server 2007:Project data is not there in Draft Database, Published database but it is there only in Reporting Database ? RRS feed

  • Question

  • Hi,

    Could anyone of you please help me here.

    We are facing one issue in project server 2007 i.e the project data is not there in Draft Database, Published database but it is there only in Reporting Database ?

    FYI, I have tried to delete the project using "Delete Enterprise Objects" with Different options

    1) Delete from Draft database and published database

    2) Delete from published database.

    In these two scenarios once I have deleted the project, it will get deleted from Reporting as well.

    Could you please let me know in which scenario it will reside project data only in Reporting database  and what are necessary steps to resolve this.

    Anyhow what ever the projects that are showing only in reporting database is not required for me.

    If we do Force Rebuild Reporting DB, will the entire reporting database will get refresh based on what is there in Published DB  or is it something different ? 

    Please suggest me the steps to resolve this.

    Thanks in advance!



    Saturday, October 25, 2014 1:57 PM

All replies

  • Hello, I'm guessing the reporting part of the delete failed when you deleted that project originally. Rebuilding the reporting database by backing up and then restoring the custom fields would probably work - make sure you do this out of hours and have full database backups first. Alternatively you could use the stored procedure in the reporting database to delete the orphaned project but again take full database backups beforehand. See this post with a similar issue: Paul

    Paul Mather | Twitter | | CPS

    Saturday, October 25, 2014 4:17 PM
  • Hi PWMather,

    Thank you for your help :)

    And I have few doubts mentioned below on this, could you please clarify?

    Is the reporting database backup mandatory for Re-building reporting database ?

    And could you please let me know what data will get refresh if we take up backup and restoring Enterprise custom fields ? Will the Entire reporting database will get refresh or how it will be ..... ?



    Sunday, October 26, 2014 4:38 PM
  • Hello,

    If it was me, I would get the ProjectUID and pass this into the MSP_EPM_DeleteProject stored procedure on the Project Server Reporting database rather than the Reporting DB rebuild. Some say the DB rebuild using the backup and restore option is "safer" but providing you have full DB backups beforehand then fully test it should be fine. To be 100% safe, I would raise a support ticket with Microsoft if you are not happy with using one of the two options. Regarding the questions you have - yes take full DB backups of all PWA database before either approach then fully test after. The reporting database will effectively get rebuilt using the backup then restore option for the enterprise custom fields - this might take a long time depending on the amount of data you have and the specs of the servers. Some links below for Reporting DB rebuilding:

    Hope that helps :)


    Paul Mather | Twitter | | CPS

    Sunday, October 26, 2014 5:36 PM