nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

schemaLockingEnabled for Geocode services

RonnieRichards

In ArcGIS Server, it would be great if Geocode services had the option to turn off schema locking like map services. This is frustrating since all operations are made against the locator anyway and a schema lock still exists on the sde feature class, why ?

schemaLockingEnabled = True/False

Find more posts tagged with

Status: Open

Comments

dewright_ca

Ronnie Richards I found the best bypass for this is to publish as a Composite; then the underlying locators aren't locked once you stop the parent service.

MelanieWawryk

In 10.2 we were able to save the geocoders in the geodatabase, publish them and then use python to update them without them being locked using a simple arcpy.RebuildAddressLocator_geocoding(in_address_locator). Now in 10.5, we have been forced to move them to a file location and now they have locks added to the mix. I agree there should be the option to not have the geocoding service lock the geocoders.

It would be nice to have a global option to never have your services lock the schema for any type of service so it doesn't have to be set for each service.