Dave:
I disagree with Sean's very limited caps, we have clients who routinely
manage schedules in excess of 5000 tasks. So, the question is what are the
characteristics of the problem schedules that is causing the problem? This
could be file bloat, especially if these schedules were created from earlier
versions of Project or if the schedules contain bad or questionable data.
For instance, blank lines in schedule files cause problems, but there are
many other factors such as excessive time-phased data, as Sean suggests.
With very large files that follow best practice in structure, it is not
unreasonable to wait a minute or more for these to save, but it shouldn't
render the system useless. The numbers that you quote indicate that 30% of
the lines in these schedules are not tasks. How many of these are blank
lines? Are you assigning resources to summary tasks? Are you setting
dependencies on summary tasks? There are many factors that can affect
performance.
--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting:
http://www.msprojectexperts.com
Project Server Training:
http://www.projectservertraining.com
Project Server FAQS:
http://www.projectserverexperts.com
Project Server Help Blog:
http://www.projectserverhelp.com