The Geodatabase database is divided into:
- Personal Geodastabase personal geodatabase,
- File Geodatabase file geodatabase,
- ArcSDE Geodatabase SDE geodatabase.
Three respectively is * .mdb, *. Gdb and SDE database. Wherein the difference between the mdb gdb and wherein:
- mdb Microsoft Access database using a data file structure, capacity is limited to 2GB, and with the large amount of data time, performance degrades, the effective size of the database is generally between 250M to 500M.
- gdb database single set of data stored reaches the upper limit can 1TB, may store a plurality of data sets.
- SDE geodatabase based on Oracle, SQL Server, Informix or DB2 relational database to build a large enterprise spatial database, you need to connect through ArcSDE, support multiple users to read and write.
| Key features |
ArcSDE geodatabases |
File Geodatabase |
Personal geodatabase |
|
| description |
Collection of various types of GIS data sets in a relational database stored in the form of a table (in a relational database to store and manage user ArcGIS GIS data recommended native data format) |
Collection of various types of GIS data set stored in the file system folder (for ArcGIS user folders in the file system stored and managed in the recommendations of the native data format) |
Raw data format MicrosoftAccess ArcGIS geodatabase data file storage and management. (The size of this data formats are limited and only available for Windows operating systems) |
|
| User number |
Multi-user: multiple readers and multiple writers |
Individual users and smaller working groups: Each feature dataset, stand-alone feature class or table has more than one writer or readers. Floating any particular file will eventually lead to downgrading of a large number of readers. |
Individual users and smaller working groups and a number of readers writer (having a smaller data sets). Concurrent Use eventually lead to downgrading of a large number of readers. |
|
| Storage format |
l Oracle l Microsoft SQL Server l IBM DB2 l IBM Informix l Netezza l PostgreSQL |
Each dataset is a separate file on disk. File Geodatabase |
All the contents of each personal geodatabase are stored in a single MicrosoftAccess |
|
| Size Limit |
DBMS limit up |
Each data set 1TB. Each file geodatabase can save a lot of data sets. For very large image dataset, 1TB limit can be increased to 256TB. Each feature class expandable up to hundreds of millions each data set element vectors. |
Each Access database 2GB. Effectively limit before degradation is typically between 250 to each of the Access database file 500MB. |
|
| Version management support |
Full support for all DBMS. Including database synchronous replication, using checkout and check to be updated and historical archiving. |
Submit updated using checkout and check for the client and one-way replication can be used to send update client only supports geographic database format. |
Submit updated using checkout and check for the client and one-way replication can be used to send update client only supports geographic database format. |
|
| platform |
Directly connected to Windows, UNIX, Linux and a DBMS, which DBMS might run on any platform the user's local network. |
Cross-platform. |
Only available for Windows. |
|
| Security and Permissions |
Provided by the DBMS |
Operating file system security. |
Windows file system security. |
|
| Database management tools |
Backup, recovery, replication, SQL support, security features such as a complete DBMS |
File system management. |
Windows file system management. |