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???
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???