<?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 Full US level SSURGO database, bad idea? in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/full-us-level-ssurgo-database-bad-idea/m-p/184575#M10419</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone have some "best practices" or "lessons learned" they'd like to share on creating a complete US level SSURGO geodatabase in SQLServer?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm creating an application that will hopefully be useful across the entire US but really hate the idea of coding a big fat 'if STATE='X' then GDB="X" to deal with the smaller data chucks that come from USDA.&amp;nbsp; Handling user AOIs that overlap state boundaries gets even uglier... &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;We've made an initial attempt at loading the dataset chucks and are close to 30M MUPOLGYON records and performance is not that great. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is ugly code better than an overtaxed database? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for any advice.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 May 2016 21:22:42 GMT</pubDate>
    <dc:creator>FredSpataro</dc:creator>
    <dc:date>2016-05-27T21:22:42Z</dc:date>
    <item>
      <title>Full US level SSURGO database, bad idea?</title>
      <link>https://community.esri.com/t5/data-management-questions/full-us-level-ssurgo-database-bad-idea/m-p/184575#M10419</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;BR /&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone have some "best practices" or "lessons learned" they'd like to share on creating a complete US level SSURGO geodatabase in SQLServer?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm creating an application that will hopefully be useful across the entire US but really hate the idea of coding a big fat 'if STATE='X' then GDB="X" to deal with the smaller data chucks that come from USDA.&amp;nbsp; Handling user AOIs that overlap state boundaries gets even uglier... &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;We've made an initial attempt at loading the dataset chucks and are close to 30M MUPOLGYON records and performance is not that great. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is ugly code better than an overtaxed database? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance for any advice.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 May 2016 21:22:42 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/full-us-level-ssurgo-database-bad-idea/m-p/184575#M10419</guid>
      <dc:creator>FredSpataro</dc:creator>
      <dc:date>2016-05-27T21:22:42Z</dc:date>
    </item>
  </channel>
</rss>

