none
MS Project SERVER - File Bloat

    Pregunta

  • Is there a way to reduce project bloat on a project schedule in Project Server 2010?    I thought that project files on Project Server should not experience bloat due to the way MSPS processes file-saves.    We saw a file increase from 18M to 29M in a week's time.  

    We are using PWA for time tracking and I don't want to lose or corrupt any data during the process.   We do have custom views, an ERP, and about 20 or so Enterprise codes (Project, Task, and Resource).  

    Any idea why project bloat occrus in MSPS and how to resolve? 

    Thanks

    Randy

    miércoles, 15 de agosto de 2012 18:55

Todas las respuestas

  • This forum is for standalone desktop edition of Project. Could you pls consider posting in Project Server forums here at ? http://social.msdn.microsoft.com/Forums/en-US/projectserver2010general/threads

    Sometimes the moderators move the thread.

    jueves, 16 de agosto de 2012 0:18
  • Try opening the file & saving it in XML format & then reimport it back should help, typically happens when schedule gets corrupted

    Let us know if it helps


    Thanks | Sunil Kr Singh | http://epmxperts.wordpress.com

    jueves, 16 de agosto de 2012 13:06
  • Thanks for letting me know.   Just a mistake on my part as I usually post to the MSPS forum.   My bad.
    jueves, 16 de agosto de 2012 14:35
  • Sunil - Thanks for the reply.   Are you certain that I won't lose anything by doing this?    This is a very large, complex and critical schedule.     Also, when I perform this excercise, after saving it off as an XML file, do I delete the file on the server before importing the off line copy back into the server?

    Thanks

    ~RK

    jueves, 16 de agosto de 2012 14:38
  • I am not totally sure if the GUID's of the tasks won't change with the XML Save procedure.

    A little bit safer option is to use the "Save file for Sharing", save it as a local desktop copy, and then save it back to the server. This kind of "refreshes" the plan without changing the GUIDs, or losing any Timesheet work. I have recently used this on a project plan which was not huge but pretty complex and critical.

    The only thing that will change ( based on what I observed so far) is the "Status Manager", if this is done by an admin. To make sure this does not happen, have the PM himself do these steps. Otherwise, take a backup of the file/column, and change the status manager back to what it should have been.

    And finally, the standard disclaimer applies: it is best to test any of these procedures in a test enviroment, to see if you experience anything unexpected.


    Prasanna Adavi, PMP, MCTS http://thinkepm.blogspot.com

    jueves, 16 de agosto de 2012 15:01