Afterwards I inserted Relationships between the activities, more than 33000 relationships, the loading process of P6.2.1 increases. While we are waiting for the appliction 1h or more runs away before the application can be managed. What is the problem of P6 which increases the loading process? Please help us as soon as possible.
Is this a stand-alone or network/enterprise database?
Oracle or MS SQL?
Is the database on your LAN or are you accessing it across the WAN?
One hour seems excessive but there are a lot of variables that can performance issues. Our primary schedule is roughly 20K activities (I'm not sure exactly how many relationships off the top of my head) and takes us 3-5 minutes to initially load.
We have tested the Indexes of the tables which are used. So we found out that the import of XER-files fragments the indexes so strong that the application needs so long for loading. We rebuild the indexes and the application starts as usually.
Therefore another question comes up, whether the MSSQL Enterprice Edition automaticly defragments the fragmented indexes. If so, then we can relay on that system, if not so, then we have to inform our customer about this problem.