Geodatabases and the production environments
The geodatabase is a "container" used to hold a collection of datasets. There are three types:
- File geodatabases—Stored as folders in a file system. Each dataset is held as a file that can scale up to 1 TB in size. The file geodatabase is recommended over personal geodatabases.
- Personal geodatabases—All datasets are stored within a Microsoft Access data file, which is limited in size to 2 GB.
- ArcSDE geodatabases—Stored in a relational database using Oracle, Microsoft SQL Server, IBM DB2, IBM Informix, or PostgreSQL. These multiuser geodatabases require the use of ArcSDE and can be unlimited in size and numbers of users.
More information about file and personal geodatabases can be found here.
More information about ArcSDE geodatabases can be found here.
Geodatabases and the enterprise production environment
In the enterprise production environment, the central database (CDR) and product library are stored in an ArcGIS Server ArcSDE geodatabase. The Nautical Solution supports Oracle 11g and Microsoft SQL Enterprise. The product databases are stored in Microsoft SQL Server Express geodatabases.
 |
Nautical enterprise production environment |
See Setting up the NIS database for steps on implementing the NIS (CDR).
Geodatabases and the desktop production environment
In the desktop environment, the product library can be implemented as either ESRI's file geodatabase or ArcSDE for SQL Express geodatabases.
For ENC, AML, and paper chart products, the product databases are stored as Microsoft SQL Server Express.
 |
Desktop S-57 and chart production environment |
For DNC products, the product databases are stored as ESRI personal geodatabases.
 |
Desktop DNC production environment |