Hoping someone can shine some light on this situation...
We are working with the Parcel Fabric in 10.1 and Enterprise ArcSDE 10.0 for storage. We have three people actively editing the fabric at any one time. The amount of data is not huge...there are about 450000 lines/ 60000 parcels etc. We are running windows xp (*cough*) 32 bit systems. Two of the editors are running on Active Directory database authentication. Novell desktop is running on top of these machines.
Almost everyday we will run into a save issue where ArcMap will take hours and hours (5-6) to save edits to the database. I know this is a needle in a haystack but has anyone run into similar behavior?...any thoughts/ideas?...what sort of traces/logs might I look into?
Also, edits on other feature classes with 50000+ features don't seem to mirror these issues.
Any help is greatly appreciated.
Thanks!!
We are working with the Parcel Fabric in 10.1 and Enterprise ArcSDE 10.0 for storage. We have three people actively editing the fabric at any one time. The amount of data is not huge...there are about 450000 lines/ 60000 parcels etc. We are running windows xp (*cough*) 32 bit systems. Two of the editors are running on Active Directory database authentication. Novell desktop is running on top of these machines.
Almost everyday we will run into a save issue where ArcMap will take hours and hours (5-6) to save edits to the database. I know this is a needle in a haystack but has anyone run into similar behavior?...any thoughts/ideas?...what sort of traces/logs might I look into?
Also, edits on other feature classes with 50000+ features don't seem to mirror these issues.
Any help is greatly appreciated.
Thanks!!