Use Ping to ping you SQL server the response time should be less than 50ms on
a LAN. If your responces time is less than 50ms but you are still getting
poor save time, your LAN support people should look at the confguration of
the SQL server NIC card(s) and there LAN connection. I have seen NIC cards
that did work well with certain hubs or switches.
If the response time is greater than 50ms because of routers filewalls and
ect. you should consider using terminals services with Project Pro and
Project Server 2003. I have seen old slow routers to also cause this
problem. You can use Tracert (trace route) to see the response time of
router in your network.
Most of the time poor save times on LANs are some kind of network hardware
issue. But it can also be that the projects are very large. Even when they
have a small number of tasks. There are many things that make a project very
large including lots of timephased actuals, large numbers of baselines, large
numbers of assignments and projects that are very long duration. Save the
trouble project as a mpp in the locate file and see how large it is. I have
seen projects as large as 40-50 meg in size, projects of this size will take
a long time to save even on a fast LAN.
Hope this helps