<?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>topic Re: Control schema locking behavior in ArcGIS Pro in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1490844#M84492</link>
    <description>&lt;P&gt;So... why not just run the script from within the Pro Python Window to get around that lock?&lt;/P&gt;</description>
    <pubDate>Wed, 12 Jun 2024 18:14:42 GMT</pubDate>
    <dc:creator>AlfredBaldenweck</dc:creator>
    <dc:date>2024-06-12T18:14:42Z</dc:date>
    <item>
      <title>Control schema locking behavior in ArcGIS Pro</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1490469#M84476</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Is there a way to load a FGDB feature class into an ArcGIS Pro map as read-only with no schema-locking?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I would like to achieve the following scenario:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Load a feature class from a file geodatabase as read-only into an ArcGIS Pro map. The point being it will not establish a schema lock, but I can view the data.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The context is - when developing Python scripts with arcpy, I will typically have a Pro project set up to inspect the results and data as I run and debug the scripts.&lt;/P&gt;&lt;P&gt;Because Pro locks the schemas when the map is loaded... I have to shut down Pro to free the lock, run my script, wait for it to complete, open Pro, and then inspect results. During the development process I may have to do this over 100 times.&lt;/P&gt;&lt;P&gt;With an enterprise GDB I can use a Query Layer to establish a read-only layer, however during development our best practice is to use localized FGDBs until the script is debugged and the data has been validated.&lt;/P&gt;&lt;P&gt;Am I missing something? Does anyone have a workaround for this? Feature Request?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 13:07:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1490469#M84476</guid>
      <dc:creator>eMosby</dc:creator>
      <dc:date>2024-06-12T13:07:10Z</dc:date>
    </item>
    <item>
      <title>Re: Control schema locking behavior in ArcGIS Pro</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1490475#M84477</link>
      <description>&lt;P&gt;Assorted thoughts:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;As a workaround, would Make Query Table do what you want?&amp;nbsp;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/consistent-visible-sql-expressions-and-query/idc-p/1366709/highlight/true#M27874" target="_blank" rel="noopener"&gt;https://community.esri.com/t5/arcgis-pro-ideas/consistent-visible-sql-expressions-and-query/idc-p/1366709/highlight/true#M27874&lt;/A&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;I like your idea of submitting a specific feature request for this.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;I see you have voted for&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://community.esri.com/t5/arcgis-pro-ideas/file-geodatabase-query-layers/idi-p/1237538" target="_self"&gt;File geodatabase query layers&lt;/A&gt;&lt;SPAN&gt;. Anyone else viewing this post could vote for it too.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;You could consider asking this question in the Python community too, if you haven't already.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;As a very last resort, maybe you could create a file geodatabase database view. Views don't lock data.&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#0000FF"&gt;SELECT * FROM YOUR_FC&lt;/FONT&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Thu, 13 Jun 2024 19:16:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1490475#M84477</guid>
      <dc:creator>Bud</dc:creator>
      <dc:date>2024-06-13T19:16:13Z</dc:date>
    </item>
    <item>
      <title>Re: Control schema locking behavior in ArcGIS Pro</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1490844#M84492</link>
      <description>&lt;P&gt;So... why not just run the script from within the Pro Python Window to get around that lock?&lt;/P&gt;</description>
      <pubDate>Wed, 12 Jun 2024 18:14:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1490844#M84492</guid>
      <dc:creator>AlfredBaldenweck</dc:creator>
      <dc:date>2024-06-12T18:14:42Z</dc:date>
    </item>
    <item>
      <title>Re: Control schema locking behavior in ArcGIS Pro</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1492007#M84548</link>
      <description>&lt;P&gt;Thanks Bud, those are good suggestions I will have to test out. At first glance an FGDB database view may be preferable because I think it would be agnostic of schema changes.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2024 18:59:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1492007#M84548</guid>
      <dc:creator>eMosby</dc:creator>
      <dc:date>2024-06-13T18:59:17Z</dc:date>
    </item>
    <item>
      <title>Re: Control schema locking behavior in ArcGIS Pro</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1492010#M84550</link>
      <description>&lt;P&gt;Mainly because I prefer my IDE, but also we require version control, multiple devs.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2024 19:02:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1492010#M84550</guid>
      <dc:creator>eMosby</dc:creator>
      <dc:date>2024-06-13T19:02:06Z</dc:date>
    </item>
    <item>
      <title>Re: Control schema locking behavior in ArcGIS Pro</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1492131#M84564</link>
      <description>&lt;P&gt;There is a &lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-file-gdb/compress-file-geodatabase-data.htm" target="_self"&gt;Compress File Geodatabase&lt;/A&gt;&amp;nbsp;GP tool that sets the GDB, FC and/or FDS to "read-only"&amp;nbsp; Might be worth an experiment.&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jun 2024 21:30:29 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/control-schema-locking-behavior-in-arcgis-pro/m-p/1492131#M84564</guid>
      <dc:creator>Robert_LeClair</dc:creator>
      <dc:date>2024-06-13T21:30:29Z</dc:date>
    </item>
  </channel>
</rss>

