<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea schemaLockingEnabled for Geocode services in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/schemalockingenabled-for-geocode-services/idi-p/959996</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;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 ?&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="color: rgb(61, 61, 61); font-family: arial,helvetica,helvetica neue,verdana,sans-serif; font-size: 14px;"&gt;schemaLockingEnabled = True/False&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;

&lt;!-- content transformation source ID: 087E0000000CxTR --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 11 May 2015 15:19:12 GMT</pubDate>
    <dc:creator>RonnieRichards</dc:creator>
    <dc:date>2015-05-11T15:19:12Z</dc:date>
    <item>
      <title>schemaLockingEnabled for Geocode services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/schemalockingenabled-for-geocode-services/idi-p/959996</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;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 ?&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="color: rgb(61, 61, 61); font-family: arial,helvetica,helvetica neue,verdana,sans-serif; font-size: 14px;"&gt;schemaLockingEnabled = True/False&lt;/SPAN&gt;&lt;BR /&gt;&amp;nbsp;

&lt;!-- content transformation source ID: 087E0000000CxTR --&gt;

&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 May 2015 15:19:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/schemalockingenabled-for-geocode-services/idi-p/959996</guid>
      <dc:creator>RonnieRichards</dc:creator>
      <dc:date>2015-05-11T15:19:12Z</dc:date>
    </item>
    <item>
      <title>Re: schemaLockingEnabled for Geocode services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/schemalockingenabled-for-geocode-services/idc-p/959997#M1295</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It would be nice to have a global option&amp;nbsp;to never have your services lock the schema for any type of service so it doesn't have to be set for each service.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Nov 2017 15:17:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/schemalockingenabled-for-geocode-services/idc-p/959997#M1295</guid>
      <dc:creator>MelanieWawryk</dc:creator>
      <dc:date>2017-11-14T15:17:03Z</dc:date>
    </item>
    <item>
      <title>Re: schemaLockingEnabled for Geocode services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/schemalockingenabled-for-geocode-services/idc-p/959998#M1296</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A _jive_internal="true" class="" data-userid="6743" data-username="rgrichards" href="https://community.esri.com/people/rgrichards" style="color: #8ca9cd; background-color: #ffffff; border: 0px; font-weight: 600; text-decoration: none; font-size: 13.7136px; padding: 0px;"&gt;Ronnie Richards&lt;/A&gt;&lt;SPAN style="color: #8b8b8b; background-color: #ffffff;"&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;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.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Mar 2018 17:20:56 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/schemalockingenabled-for-geocode-services/idc-p/959998#M1296</guid>
      <dc:creator>DEWright_CA</dc:creator>
      <dc:date>2018-03-26T17:20:56Z</dc:date>
    </item>
  </channel>
</rss>

