Geo-Database Corruption in a versioned 10.3 environment

المشرف العام

Administrator
طاقم الإدارة
This is not so much a direct question as it is a request for any information or experiences others may have had with issues similar to this and how they went about mitigating them.

A little history:

We are the EGIS group for a rather large city and using ARCSDE and ARCDESKTOP v 10.3 in a versioned environment to manage public works service requests. We recently upgraded our desktop versions from 10.0 to 10.3 while our ArcSDE stayed in version 9.3 (we had to keep it in 9.3 rather long to support legacy apps) After upgrading the desktops to 10.3 the performance of our web maps/services and our desktops went to hell. Web maps would take 10+ minutes to load the geodatabases and saving edits in arc desktop would take a similar amount of time.

We had a couple of new test servers already installed and running ARCSDE 10.3 so we migrated our 9.3 GDB to the 10.3 server, when we did this the 9.3 server showed 93,115 records but after the transfer to 10.3 the records only showed 93,002 records (113 records were lost.) After the transfer the performance went back to normal and all of the previously mentioned problems were solved.

Fast forward 2 weeks and we are experiencing the same performance issues as before with the ARCGISONLINE web maps taking forever to load and editing in desktop 10.3 taking forever. On a side note we are using versioning with some people (mainly data entry, planners, analysts) editing data on the children with the EGIS people editing data directly into the parent.

My questions are: What could be causing these issues? Are we corrupting the gdb through our current practices? What steps can we take to mitigate these issues? Has anyone else experienced similar problems and if so what were your solutions?



أكثر...
 
أعلى