Tuesday, June 12, 2012 7:08 PM
There is a project that is being used at my company that has about 3500 assignments and 250 resources. My problem is that when one of our project managers publish the plan. Project Server kicks in and starts running. After 4 hours the Project Server changes the state of the job in the Project Server queue to failed, but the SQL Server stays processing.
My question is what do I need to do to determine what the SQL Sever is processing and more importantly, when the SQL Server queue job is finished.
Wednesday, June 13, 2012 5:08 AM
There can be two states on job failures in Manage queue of Project server - Failed and Not Blocking correlation & Failed and Blocking correlation. WHich one do you see in Manage queue of PWA server settinsg for the project?
As per project size standards, a project with 3500 assignments & 250 resources is large size project but this shouldn't take 4 hours. How about number of custom fields on project/task & calculated custom fields in project? How many baselines do you have for project?
Can you please post the exact error from Manage queue under PWA server settings & ULS logs to find the cause of the error. Sounds like bad data of project is causing this.
Please see Brian's article:
If you found this post helpful, please “Vote as Helpful”. If it answered your question, please “Mark as Answer”. Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
Friday, July 20, 2012 8:29 PMSorry for the delay. We also had Microsoft working on this as well. The number of calculated custom fields are about 75. It generates about 1.8 million records in the log. We are inching along until the project finishes in about 3 months....then they get 5 if any calculated custom fields.
Saturday, July 21, 2012 6:32 PM
Wow. 75 calculated fields? The average I see is usually 5 or less. Have you followed the performance recommendations for SQL? http://blogs.technet.com/b/projectadministration/archive/2009/12/04/sql-server-settings-for-performance-recommendations.aspx
If you are doing this for BI purposes, it's better to move this either into OLAP or one of the BI tools. I try to keep calculated fields to needs that are transactional in nature.
Treb Gatte @tgatte
- Marked As Answer by Fred.Simons.Apex Thursday, July 26, 2012 12:55 PM
Thursday, July 26, 2012 12:55 PM
Wow is correct. This Project was created way before I got here. We are limping along until this project dies....hopefully in about 4 months. We are having the department create projects and subprojects and keeping the calculated fields down to the max of 5 if any.
They created them because they were there....kind of like "build it and they will come." This has been a maintenance monster and when I created this forums request it was getting out of control.
Thanks for all the input.