PDMS hangs up after deleting any item

There are a couple of things that you have said that might  imply maybe this isn't network.... can you confirm.....

1. The troublesome project slows down on ONLY on delete command..... adding model content running clash checks etc are all bumbling along at a good speed.

2. The server that this troublesome project has other PDMS projects stored on it.... and these other projects on the SAME server/SAME partition are not slowing down.

I know that your first thought DRAFT is number of users.... can anyone else (apart from me) confirm that PDMS doesn't have performance issues like this through having many users.? How many have been seen working happily in a single DB? Like I said I have 30-40.... at what number would you get nervous? :)

[QUOTE=Big_G;42223]There are a couple of things that you have said that might  imply maybe this isn't network.... can you confirm.....

1. The troublesome project slows down on ONLY on delete command..... adding model content running clash checks etc are all bumbling along at a good speed.

2. The server that this troublesome project has other PDMS projects stored on it.... and these other projects on the SAME server/SAME partition are not slowing down.



yes..
confirmed

What is the member count under each zone?.....we have faced this issue for support database in one of our project. A zone having more then 400 member counts used to slow down the process as we had recognized while creating,modifying or deleting a support. So we did build the hierarchy such that each zone contains not more than 300 supports.

What is the member count under each zone?.....we have faced this issue for support database in one of our project. A zone having more then 400 member counts used to slow down the process as we had recognized while creating,modifying or deleting a support. So we did build the hierarchy such that each zone contains not more than 300 supports.

We also have 90% of the piping under one site but in different zones.
may this is the problem??!!

i assume there may not be 400 zones under one site :-)........................What is the member count on each zone i.e Number of pipes under each zone.

i assume there may not be 400 zones under one site :-)........................What is the member count on each zone i.e Number of pipes under each zone.

number of zones is 81.
number of pipes is about 3600 but not segregated equally under the zones.

This is an interesting one.. I have not seen this kind of problem before. You are at and slightly beyond my reach for a known fix :(

It does kind of seem that this might be a database performance issue... The point just made (about lots of members under one parent) affects not just the deleting but the navigation, and general speed of the database, commonly seen after a large implant conversion or whatever it slows up the DB considerably BUT not all the DB (only slow when accessing the bit with many many members) and not just for delete . I think your problem is a distinct one, from what I have gathered ONLY delete command, ONLY in design, ONLY on this database and ONLY when you have many users. There are two routes that I would pursue.

1. There is something that is not up to date with this database....but you have already said it is DICE, merged, not massive... there isn't too much left that I can think of. Perhaps Map Build it? It is possible that if the spatial map is out of date this *might* affect the speed just another piece of house keeping maybe you have already done this.

2. Try a reconfigure.... perhaps DICE has missed something. Perhaps there is something structurally wrong with db.... might be a good time to separate piping and equi.

I am fast running out of ideas :( Anyone think of anything else???

Sorry to post twice but I just some maths.... 3600 pipes in 81 zones...44 members per zone on ave. Though you did say these are not evenly distributed. This seems a bit high to me but not hugely.

What are the maximum no of Pipes under a zone?

What are the maximum no of Pipes under a zone?

the maximum no of Pipes under a zone is 383