<?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 Database connection performance in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/database-connection-performance/m-p/1078597#M43436</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I wanted to look into our database performance, since every time we open a connection to it, it takes around 20 to 30 seconds to open. We have an enterprise geodatabase in SQL Server, and have around 700 feature classes in it. So I am wondering if 30 seconds is a normal time to wait for such a database connection to open. It seems ArcGIS Pro is a little bit faster than ArcMap.&lt;/P&gt;&lt;P&gt;I used sdeintercept to create a log and found that there is one big time consuming operation, which is the ExecuteSpatialQuery, by far the most time consuming step in the whole log.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am wondering why a spatial query needs to be executed when opening a database connection.&lt;/P&gt;&lt;P&gt;Here's a sample:&lt;BR /&gt;========================================&lt;BR /&gt;[W 16:42.941] Command: GetDbmsInfo&lt;BR /&gt;[R 16:42.941] Long: 0&lt;BR /&gt;[R 16:42.941] Long: 5&lt;BR /&gt;[R 16:42.941] Long: 1096810511&lt;BR /&gt;========================================&lt;BR /&gt;[W 16:42.941] Command: ExecuteSpatialQuery&lt;BR /&gt;[W 16:42.941] Long: 1&lt;BR /&gt;[R 17:02.648] Long: 0&lt;BR /&gt;========================================&lt;BR /&gt;[W 17:02.648] Command: NextBuffer&lt;/P&gt;&lt;P&gt;I hope anyone can shed some light on this, and would also like comments on whether this is a normal wait time for opening an enterprise geodatabase with such a number of feature classes.&lt;/P&gt;&lt;P&gt;Joris&lt;/P&gt;</description>
    <pubDate>Wed, 14 Jul 2021 08:15:44 GMT</pubDate>
    <dc:creator>jorisfrenkel</dc:creator>
    <dc:date>2021-07-14T08:15:44Z</dc:date>
    <item>
      <title>Database connection performance</title>
      <link>https://community.esri.com/t5/data-management-questions/database-connection-performance/m-p/1078597#M43436</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I wanted to look into our database performance, since every time we open a connection to it, it takes around 20 to 30 seconds to open. We have an enterprise geodatabase in SQL Server, and have around 700 feature classes in it. So I am wondering if 30 seconds is a normal time to wait for such a database connection to open. It seems ArcGIS Pro is a little bit faster than ArcMap.&lt;/P&gt;&lt;P&gt;I used sdeintercept to create a log and found that there is one big time consuming operation, which is the ExecuteSpatialQuery, by far the most time consuming step in the whole log.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am wondering why a spatial query needs to be executed when opening a database connection.&lt;/P&gt;&lt;P&gt;Here's a sample:&lt;BR /&gt;========================================&lt;BR /&gt;[W 16:42.941] Command: GetDbmsInfo&lt;BR /&gt;[R 16:42.941] Long: 0&lt;BR /&gt;[R 16:42.941] Long: 5&lt;BR /&gt;[R 16:42.941] Long: 1096810511&lt;BR /&gt;========================================&lt;BR /&gt;[W 16:42.941] Command: ExecuteSpatialQuery&lt;BR /&gt;[W 16:42.941] Long: 1&lt;BR /&gt;[R 17:02.648] Long: 0&lt;BR /&gt;========================================&lt;BR /&gt;[W 17:02.648] Command: NextBuffer&lt;/P&gt;&lt;P&gt;I hope anyone can shed some light on this, and would also like comments on whether this is a normal wait time for opening an enterprise geodatabase with such a number of feature classes.&lt;/P&gt;&lt;P&gt;Joris&lt;/P&gt;</description>
      <pubDate>Wed, 14 Jul 2021 08:15:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/database-connection-performance/m-p/1078597#M43436</guid>
      <dc:creator>jorisfrenkel</dc:creator>
      <dc:date>2021-07-14T08:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: Database connection performance</title>
      <link>https://community.esri.com/t5/data-management-questions/database-connection-performance/m-p/1079685#M43440</link>
      <description>&lt;P&gt;If you actually trace the SDE API calls, you'll see it's not the connecting, &lt;EM&gt;per se&lt;/EM&gt;, but the need to inventory the objects present so they can be symbolized in the UI.&amp;nbsp; There are queries to list tables, and feature classes, and feature datasets, and rasters, and raster datasets,...&amp;nbsp; Then for feature classes, the geometry type needs to be queried, so the right icon is used. So yes, thirty seconds is not completely unreasonable for 700 tables.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2021 15:18:21 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/database-connection-performance/m-p/1079685#M43440</guid>
      <dc:creator>VinceAngelo</dc:creator>
      <dc:date>2021-07-16T15:18:21Z</dc:date>
    </item>
    <item>
      <title>Re: Database connection performance</title>
      <link>https://community.esri.com/t5/data-management-questions/database-connection-performance/m-p/1080145#M43450</link>
      <description>&lt;P&gt;Thanks, that's very useful.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Jul 2021 06:40:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/database-connection-performance/m-p/1080145#M43450</guid>
      <dc:creator>jorisfrenkel</dc:creator>
      <dc:date>2021-07-19T06:40:11Z</dc:date>
    </item>
  </channel>
</rss>

