<?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 Globally Set Lock Database Schema when Publishing Services in ArcGIS Enterprise Ideas</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-ideas/globally-set-lock-database-schema-when-publishing/idi-p/922497</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;We like to have all of our&amp;nbsp;web services&amp;nbsp;with database locking&amp;nbsp;turned off.&amp;nbsp; When the schema is locked the services can prevent SDE from compressing. I would like to change this so when we add a new web service, it is database locking unchecked (false) by default rather than checked (true).&amp;nbsp; There&amp;nbsp;should be a&amp;nbsp;config file somewhere that can be changed so the default is set to false but there doesn't seem to be.&amp;nbsp; I realize that we can easily change it every single time I add a web service but it only takes on to be forgotten to cause issues and if it is on by default it should also be able to be off by default.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;&amp;nbsp;&lt;A href="https://community.esri.com/migrated-users/3685"&gt;Tanu Hoque&lt;/A&gt;‌ &lt;A href="https://community.esri.com/migrated-users/111528"&gt;Nidhin Karthikeyan&lt;/A&gt;‌ &lt;A href="https://community.esri.com/migrated-users/7009"&gt;brian bieber&lt;/A&gt;‌ &lt;A href="https://community.esri.com/migrated-users/15902"&gt;Alison Gaiser&lt;/A&gt;‌ &lt;A href="https://community.esri.com/migrated-users/21272"&gt;Jason Greenlaw&lt;/A&gt;‌&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;&lt;A href="https://community.esri.com/thread/83027"&gt;behavior&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Jul 2018 15:16:11 GMT</pubDate>
    <dc:creator>MelanieWawryk</dc:creator>
    <dc:date>2018-07-03T15:16:11Z</dc:date>
    <item>
      <title>Globally Set Lock Database Schema when Publishing Services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/globally-set-lock-database-schema-when-publishing/idi-p/922497</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;We like to have all of our&amp;nbsp;web services&amp;nbsp;with database locking&amp;nbsp;turned off.&amp;nbsp; When the schema is locked the services can prevent SDE from compressing. I would like to change this so when we add a new web service, it is database locking unchecked (false) by default rather than checked (true).&amp;nbsp; There&amp;nbsp;should be a&amp;nbsp;config file somewhere that can be changed so the default is set to false but there doesn't seem to be.&amp;nbsp; I realize that we can easily change it every single time I add a web service but it only takes on to be forgotten to cause issues and if it is on by default it should also be able to be off by default.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;&amp;nbsp;&lt;A href="https://community.esri.com/migrated-users/3685"&gt;Tanu Hoque&lt;/A&gt;‌ &lt;A href="https://community.esri.com/migrated-users/111528"&gt;Nidhin Karthikeyan&lt;/A&gt;‌ &lt;A href="https://community.esri.com/migrated-users/7009"&gt;brian bieber&lt;/A&gt;‌ &lt;A href="https://community.esri.com/migrated-users/15902"&gt;Alison Gaiser&lt;/A&gt;‌ &lt;A href="https://community.esri.com/migrated-users/21272"&gt;Jason Greenlaw&lt;/A&gt;‌&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #ffffff;"&gt;&lt;A href="https://community.esri.com/thread/83027"&gt;behavior&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Jul 2018 15:16:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/globally-set-lock-database-schema-when-publishing/idi-p/922497</guid>
      <dc:creator>MelanieWawryk</dc:creator>
      <dc:date>2018-07-03T15:16:11Z</dc:date>
    </item>
    <item>
      <title>Re: Globally Set Lock Database Schema when Publishing Services</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/globally-set-lock-database-schema-when-publishing/idc-p/1088537#M2579</link>
      <description>&lt;P&gt;Alternatively, but equally valuable, is an option to configure it ourselves.&lt;/P&gt;&lt;P&gt;We're in the same boat and have had to set each map service individually, and regardless how we do it, it's not a simple checkbox - it's in the Advanced Settings, buried too deep to make it a quick item to address. But, as someone else identified in a discussion on it, by configuring a default&amp;nbsp; value alleviates having to do it every time, ensuring that the setting is correct, as opposed to allowing potential user error (forgetfulness/busy/pre-occupied etc).&lt;/P&gt;</description>
      <pubDate>Thu, 12 Aug 2021 17:04:45 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/globally-set-lock-database-schema-when-publishing/idc-p/1088537#M2579</guid>
      <dc:creator>AbeCoughlin</dc:creator>
      <dc:date>2021-08-12T17:04:45Z</dc:date>
    </item>
    <item>
      <title>Re: Globally Set Lock Database Schema when Publishing Services - Status changed to: Under Consideration</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-ideas/globally-set-lock-database-schema-when-publishing/idc-p/1243035#M3106</link>
      <description />
      <pubDate>Wed, 21 Dec 2022 18:34:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-ideas/globally-set-lock-database-schema-when-publishing/idc-p/1243035#M3106</guid>
      <dc:creator>jill_es</dc:creator>
      <dc:date>2022-12-21T18:34:17Z</dc:date>
    </item>
  </channel>
</rss>

