![The Backend Engineering Show with Hussein Nasser artwork](https://is1-ssl.mzstatic.com/image/thumb/Podcasts113/v4/cd/d5/bb/cdd5bbe4-0e12-9615-1bd5-6f578f2e6875/mza_5436295260688338257.jpg/100x100bb.jpg)
Episode 87 - Q&A - When to use Shape File vs Geodatabase?
The Backend Engineering Show with Hussein Nasser
English - February 09, 2019 21:56 - 10 minutes - 9.68 MB - ★★★★★ - 5 ratingsTechnology Homepage Download Apple Podcasts Google Podcasts Overcast Castro Pocket Casts RSS feed
Previous Episode: Episode 86 - Recycling in ArcGIS Server
Next Episode: Episode 88 - What was wrong with SOAP Protocol?
In this episode we answer a question from Anthony.
How do you know when to focus on building a geodatabase (let's say SQL server database) rather than just let the data sit in the shapefile?
I would say if you are planning to have multiple users accessing and editing the data, also if your data grew too large shape files might not be scalable to read. Also if you are planning to use the capabilities of Geodatabase such as domains, subtypes, attribute rules, versioning, archiving etc not to mention sharing as well. if you wont plan to use any of the above then shape file is a good choice. If you are planning to just maintain a shape file data of 10k or 100k features and you edit it yourself locally it works!