none
MSP 2007- Applying updates SP2 has caused customizations in the database to be lost? RRS feed

  • Question

  • We applied SP2 to MSP 2007 Sp1 and the additional code calls that we had written in

    1) Timesheet events-Reporting database

    2) Project checkin event - Draft database

    have been lost. Why did this happen and does this indicate any other problem?

    Thanks in advance.

    Wednesday, June 22, 2011 7:17 AM

Answers

  • There you go ..found the culprit . I was suspecting something like this :)

    Only the Reporting database schema is documented. You should access the Draft, Published, and Archive databases only through the PSI. You can add data tables, fields (properties), and entities that are not defined in the Project Server 2007 database schema to the Reporting database. If you add tables, fields (properties), and entities that are not defined in Project Server 2007 to the core databases, you must also provide the full stack of a custom assembly, Web service, business objects, and data access. You can easily modify the Reporting database, but I recommend that you do not modify the core Project Server databases."

    So when you applied the SP2, It removed all the customization in Draft DB but I wonder why SP2 deployment was successful. should have thrown the error message.

    1. Try to remove those customization & use the SQL job (by querying the reporting db) / PSI calls to send emails for a project changes

    2. Use PSI /Project server event handler whenever a TS status is changes, send email.

    Hope that helps.


    Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
    Wednesday, June 22, 2011 9:46 AM

All replies

  • Hello msp admin,

    I am not very clear about the customization what you did but from the subject line it seems that some customization in database are lost on applying the SP2.

    To be clear, If you modify the database schema on project server draft/published/archive, It is NOt supported as a SP/CU/patch might change the schema & your custom application./code might be broken.

    But as long as you are making PSI calls to above mentioned databases, Service pack supports the changes.

    Could you please provide more details about your customization on project server 2007?

     

     


    Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
    Wednesday, June 22, 2011 8:31 AM
  • Hi Amit,

    Thanks for your replies.

    We had changed the event MSP_PROJECT_CHECKIN_PROJECT in the Draft database so that when changes are made to Projects the authors get mails telling them about the changes.

    We had also changed MSP_TS_ChangeStatus in Reporting so that Users received emails when their Timesheets are approved or rejected.

    All these changes are lost and the users aren't getting the emails any longer. Although the stored procedures we had created (user defined) are still present in the system.

    Thanks again.

    Wednesday, June 22, 2011 9:31 AM
  • There you go ..found the culprit . I was suspecting something like this :)

    Only the Reporting database schema is documented. You should access the Draft, Published, and Archive databases only through the PSI. You can add data tables, fields (properties), and entities that are not defined in the Project Server 2007 database schema to the Reporting database. If you add tables, fields (properties), and entities that are not defined in Project Server 2007 to the core databases, you must also provide the full stack of a custom assembly, Web service, business objects, and data access. You can easily modify the Reporting database, but I recommend that you do not modify the core Project Server databases."

    So when you applied the SP2, It removed all the customization in Draft DB but I wonder why SP2 deployment was successful. should have thrown the error message.

    1. Try to remove those customization & use the SQL job (by querying the reporting db) / PSI calls to send emails for a project changes

    2. Use PSI /Project server event handler whenever a TS status is changes, send email.

    Hope that helps.


    Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
    Wednesday, June 22, 2011 9:46 AM
  • Thanks Amit, that was very useful.
    Friday, July 1, 2011 10:24 AM