<?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: SQL Server 2012 and 2008:   Geometry Performance in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/sql-server-2012-and-2008-geometry-performance/m-p/395607#M22679</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SQL 2012 introduced autogrid (with 8 levels), but legacy SDE spatial tables will still use the 4-level index unless you specifically recreate the index. I've found that starting with 1024 cells with autogrid is worth at least a 10% increase in draw times for large tables. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 Nov 2015 15:55:15 GMT</pubDate>
    <dc:creator>ThomasColson</dc:creator>
    <dc:date>2015-11-27T15:55:15Z</dc:date>
    <item>
      <title>SQL Server 2012 and 2008:   Geometry Performance</title>
      <link>https://community.esri.com/t5/data-management-questions/sql-server-2012-and-2008-geometry-performance/m-p/395606#M22678</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hello-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Has anyone experienced increased I/O performance with SQL Server 2012 vs. 2008 when using Sql Geometry?&amp;nbsp; We have found that by modifying the default spatail index from: Medium for all four levels with 16 cells per object, to Medium for levels 1-3, Low for Level 4 with 64 cells per object significantly increased draw speeds since 10.1 for large complex layers such as Parcels and have been using this index ever since.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Does anyone know if the SQL Server 2012 daatabase engine handles Sql Geometry more efficiently?&amp;nbsp; Our sde currently resindes on a Windows Server 2008R2 with 16 cores (no hyperthreading!) and 64-gb of RAM with a RAID 10 configuration.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;David&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Jun 2014 15:16:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sql-server-2012-and-2008-geometry-performance/m-p/395606#M22678</guid>
      <dc:creator>DavidColey</dc:creator>
      <dc:date>2014-06-30T15:16:42Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Server 2012 and 2008:   Geometry Performance</title>
      <link>https://community.esri.com/t5/data-management-questions/sql-server-2012-and-2008-geometry-performance/m-p/395607#M22679</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;SQL 2012 introduced autogrid (with 8 levels), but legacy SDE spatial tables will still use the 4-level index unless you specifically recreate the index. I've found that starting with 1024 cells with autogrid is worth at least a 10% increase in draw times for large tables. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Nov 2015 15:55:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/sql-server-2012-and-2008-geometry-performance/m-p/395607#M22679</guid>
      <dc:creator>ThomasColson</dc:creator>
      <dc:date>2015-11-27T15:55:15Z</dc:date>
    </item>
  </channel>
</rss>

