<?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 SQL Server Performance with large datsets in ArcGIS Enterprise Questions</title>
    <link>https://community.esri.com/t5/arcgis-enterprise-questions/sql-server-performance-with-large-datsets/m-p/530612#M20554</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We recently shifted to a new server for SQL storage. It is SQL Server 2016 the server has 24 GB of Ram and 4 sockets. We noticed a decline in performance of our larger data sets like contours. In looking at the SQL Activity monitor the queries for contours are consistently an "Expensive Query". I have added an index to one of the fields with a small amount of benefit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A difference that I am seeing for the queries being passed to SQL is the spatial methods being passed. On the old server running SDE 10.3.1 this query is passed to the contours.&lt;BR /&gt;select SHAPE from GISdw.L.Contours1Foot WHERE CONTOURS1FOOT.SHAPE.Filter (@P1) = 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While in the new server running 10.6.1 this query is being passed&amp;gt;&lt;BR /&gt;select SHAPE, CONTOURTYPE, GISDW.DCL.CONTOURS1FOOT.GDB_GEOMATTR_DATA from GISdw.DCL.Contours1Foot where CONTOURS1FOOT.SHAPE.STIntersects (@P1) = 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone else seen this behavior or have a suggested fix?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Feb 2020 17:07:53 GMT</pubDate>
    <dc:creator>DaveWatson</dc:creator>
    <dc:date>2020-02-27T17:07:53Z</dc:date>
    <item>
      <title>SQL Server Performance with large datsets</title>
      <link>https://community.esri.com/t5/arcgis-enterprise-questions/sql-server-performance-with-large-datsets/m-p/530612#M20554</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We recently shifted to a new server for SQL storage. It is SQL Server 2016 the server has 24 GB of Ram and 4 sockets. We noticed a decline in performance of our larger data sets like contours. In looking at the SQL Activity monitor the queries for contours are consistently an "Expensive Query". I have added an index to one of the fields with a small amount of benefit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A difference that I am seeing for the queries being passed to SQL is the spatial methods being passed. On the old server running SDE 10.3.1 this query is passed to the contours.&lt;BR /&gt;select SHAPE from GISdw.L.Contours1Foot WHERE CONTOURS1FOOT.SHAPE.Filter (@P1) = 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;While in the new server running 10.6.1 this query is being passed&amp;gt;&lt;BR /&gt;select SHAPE, CONTOURTYPE, GISDW.DCL.CONTOURS1FOOT.GDB_GEOMATTR_DATA from GISdw.DCL.Contours1Foot where CONTOURS1FOOT.SHAPE.STIntersects (@P1) = 1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone else seen this behavior or have a suggested fix?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Feb 2020 17:07:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-enterprise-questions/sql-server-performance-with-large-datsets/m-p/530612#M20554</guid>
      <dc:creator>DaveWatson</dc:creator>
      <dc:date>2020-02-27T17:07:53Z</dc:date>
    </item>
  </channel>
</rss>

