see http://wiki.gis.com/wiki/index.php/Server_Software_Performance
After days of troubleshooting the services I finally called ESRI Tech Support. They determined that everything was fine with my server and my services but there was definite heavy SQL usage. So, their database team called me and seemed to instantly know what my problem was. It was the new "DEFAULTS" value for GEOMETRY_STORAGE in the dbtune table. In previous versions it was set to SDEBINARY, now in 10.1 it is set to GEOMETRY which is slower. I recreated my database feature classes using the SDEBINARY for the spatial type and everything is back up to the same speed as it was in 10.0I used the sde command line tools to change the default setting to be SDEBINARY so that future feature classes that are created will use that. If we find that we need GEOMETRY for the spatial storage type we can always select it.Thanks,Luci
Hey Jamal,We thought about going back to a file geodatabase but decided against it. Some of our users wanted to be able to do tasks in our web app which would require a feature layer. Because feature layers are only supported through SQL, we would have had a portion of our data in a SQL GDB and a portion in a file GDB and that would have been too much to maintain. So far we are happy with the speed we achieved just by changing the spatial data type from Geometry to SDEBinary.We have an end of the day cleanup where all users reconcile/post and remove their versions. The data is then QC'd, reconcile/post to Default, Synchronized and the geodatabase is compressed. We Analyze about once a week. Having a good cleanup routine definitely helps with the speed of the geodatabase.Good Luck!Luci
Hi Jamal,1. Unfortunately, No, I do not know of a method to change more than one at a time from Geometry to SDEBinary.2. No, I dont think that having the versions remain will slow it down to much. I have only experienced lag when we have had major edit sessions and over 100,000 features were changed. As soon as we reconciled, posted, and compressed everything sped back up. We just have everyone delete their version at the end of the day so we know they have done the reconcile and post to our QC version. If someone wants a version to do what-if scenarious that will not be posted to Default then we allow that one to remain.3. I dont see a problem with doing it daily. We are probably smaller than most GIS departments and just find that end of week works for us. Good Luck!Luci
Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.