Does anyone have some "best practices" or "lessons learned" they'd like to share on creating a complete US level SSURGO geodatabase in SQLServer?
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. Handling user AOIs that overlap state boundaries gets even uglier...
We've made an initial attempt at loading the dataset chucks and are close to 30M MUPOLGYON records and performance is not that great.
Is ugly code better than an overtaxed database?
Thanks in advance for any advice.