<?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: Create SQL Server Index on [GDB_TO_DATE] column? in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/create-sql-server-index-on-gdb-to-date-column/m-p/1599985#M41904</link>
    <description>&lt;P&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;gdb_to_date&lt;/FONT&gt;&lt;/STRONG&gt; is part of Archiving, not Versioning, &lt;EM&gt;per se&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;Enabling Archiving creates a bunch of indexes on the _H table. It's not generally necessary to create additional indexes (which could harm performance more than help it), and doing so outside of supported tools might result in issues upgrading your geodatabase.&lt;/P&gt;&lt;P&gt;This seems to be an XY Problem question. Instead of asking about the solution you're working, it might be better to ask about the root problem, of archived table performance.&amp;nbsp; It's quite possible that the table size and database server characteristics have a lot more to do with this query latency than an index on a column with low selectivity. (How many rows in the table are there, and how many of them have been deleted?)&lt;/P&gt;&lt;P&gt;Note that this is probably more of a geodatabase (Data Management) question than an Enterprise one.&amp;nbsp;&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;</description>
    <pubDate>Thu, 27 Mar 2025 15:56:57 GMT</pubDate>
    <dc:creator>VinceAngelo</dc:creator>
    <dc:date>2025-03-27T15:56:57Z</dc:date>
    <item>
      <title>Create SQL Server Index on [GDB_TO_DATE] column?</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/create-sql-server-index-on-gdb-to-date-column/m-p/1599948#M41903</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Background&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I maintain an ArcGIS Enterprise Portal v11.3.0, with a SQL Server data source.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Problem&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;We have an Experience Builder app whose REST API calls were running slowly (8 seconds for initial page load). I traced the speed issues back to the database server.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;What I've tried&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I consulted SQL Server's Missing Indexes table, and it suggested indexing the&amp;nbsp; [GDB_TO_DATE] column (which I believe is part of the versioning feature).&lt;/P&gt;&lt;P&gt;Running SQL Profiler, I see that the Experience Builder queries always include the following,&amp;nbsp;which I assume means "return the current version of the record".&lt;/P&gt;&lt;LI-CODE lang="sql"&gt;WHERE GDB_TO_DATE = '9999-12-31 23:59:59'&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've been told that it's preferable to manipulate the ArcGIS database via ESRI tools. But when I attempted to create an Attribute Index against [GDB_TO_DATE], it's not an option in the list of columns.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Question&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1. Is it safe to bypass ESRI tools and create the index directly on SQL Server ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. If not, then is there a way to create this index with ESRI tools?&lt;/P&gt;&lt;P&gt;3. Is there a different way to resolve the slow Experience Builder queries?&lt;/P&gt;</description>
      <pubDate>Thu, 27 Mar 2025 14:30:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/create-sql-server-index-on-gdb-to-date-column/m-p/1599948#M41903</guid>
      <dc:creator>Walter</dc:creator>
      <dc:date>2025-03-27T14:30:11Z</dc:date>
    </item>
    <item>
      <title>Re: Create SQL Server Index on [GDB_TO_DATE] column?</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/create-sql-server-index-on-gdb-to-date-column/m-p/1599985#M41904</link>
      <description>&lt;P&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;gdb_to_date&lt;/FONT&gt;&lt;/STRONG&gt; is part of Archiving, not Versioning, &lt;EM&gt;per se&lt;/EM&gt;.&lt;/P&gt;&lt;P&gt;Enabling Archiving creates a bunch of indexes on the _H table. It's not generally necessary to create additional indexes (which could harm performance more than help it), and doing so outside of supported tools might result in issues upgrading your geodatabase.&lt;/P&gt;&lt;P&gt;This seems to be an XY Problem question. Instead of asking about the solution you're working, it might be better to ask about the root problem, of archived table performance.&amp;nbsp; It's quite possible that the table size and database server characteristics have a lot more to do with this query latency than an index on a column with low selectivity. (How many rows in the table are there, and how many of them have been deleted?)&lt;/P&gt;&lt;P&gt;Note that this is probably more of a geodatabase (Data Management) question than an Enterprise one.&amp;nbsp;&lt;/P&gt;&lt;P&gt;- V&lt;/P&gt;</description>
      <pubDate>Thu, 27 Mar 2025 15:56:57 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/create-sql-server-index-on-gdb-to-date-column/m-p/1599985#M41904</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2025-03-27T15:56:57Z</dc:date>
    </item>
    <item>
      <title>Re: Create SQL Server Index on [GDB_TO_DATE] column?</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/create-sql-server-index-on-gdb-to-date-column/m-p/1600097#M41912</link>
      <description>&lt;P&gt;Thanks for the reply Vince.&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;gdb_to_date&lt;/FONT&gt;&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;is part of Archiving, not Versioning,&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;per se&lt;/EM&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;I misspoke in my OP, the table in question has Archiving enabled, not Versioning.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;Enabling Archiving creates a bunch of indexes on the _H table&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;I don't have any _H tables.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;How many rows in the table are there, and how many of them have been deleted&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Total Rows: 7,040,948&lt;BR /&gt;Deleted Rows: 6,926,377&lt;BR /&gt;Difference: 114,571&lt;/P&gt;&lt;P&gt;Do these numbers look bad? Is that why queries are so slow?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;&lt;SPAN&gt;Note that this is probably more of a geodatabase (Data Management) question ...&lt;/SPAN&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I apologize for the mix up. This is my first time posting on these forums, can the post be moved?&lt;/P&gt;&lt;P&gt;Also, I'm not actually that proficient in ArcGIS knowledge, I'm a developer/sysop providing technical support to my GIS colleague.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Mar 2025 19:45:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/create-sql-server-index-on-gdb-to-date-column/m-p/1600097#M41912</guid>
      <dc:creator>Walter</dc:creator>
      <dc:date>2025-03-27T19:45:47Z</dc:date>
    </item>
  </channel>
</rss>

