ArcGIS Desktop

  • ArcGIS Pro
  • ArcMap

  • ArcGIS Pro
  • ArcMap
ArcGIS Desktop

ArcGIS Online

The mapping platform for your organization

ArcGIS Desktop

A complete professional GIS

ArcGIS Enterprise

GIS in your enterprise

ArcGIS Developers

Tools to build location-aware apps

ArcGIS Solutions

Free template maps and apps for your industry

ArcGIS Marketplace

Get apps and data for your organization

  • ArcGIS Pro
  • ArcMap
Esri
English
  • English
  • Deutsch
  • Español
  • Français
  • 日本語
  • Русский
  • 简体中文
  • Sign In
user
  • My Profile
  • Sign Out

ArcMap

  • Home
  • Get Started
  • Map
  • Analyze
  • Manage Data
  • Tools
  • Extensions
  • Manage Data
  • Geodatabases
  • Designing a geodatabase
  • Back to Top

An overview of the geodatabase

  • What is a geodatabase?
  • The architecture of a geodatabase
  • A quick tour of the geodatabase
  • Essential readings about the geodatabase
  • Table basics
  • Feature class basics
  • Raster basics
  • Types of geodatabases
  • Client and geodatabase compatibility
  • Geodatabase upgrades
  • Geodatabase functionality in ArcGIS Desktop Basic

Designing a geodatabase

  • An overview of geodatabase design
  • Geodatabase design steps
  • Using ArcGIS data model designs
  • Documenting your geodatabase design
  • Modeling feature classes
  • A note about the use of UML for geodatabase design
  • Design tips

Creating a geodatabase

  • An overview of creating geodatabases
  • A comparison of geodatabase types
  • Create a personal geodatabase
  • Create a file geodatabase
  • Create a desktop or workgroup geodatabase
  • Create an enterprise geodatabase

Working with geodatabase schema

  • Schema locking
  • About copying the schema of a geodatabase
  • Exporting a geodatabase schema to an XML workspace document
  • Importing a geodatabase schema from an XML workspace document
  • Copying a geodatabase schema using Extract Data Wizard in ArcMap
  • Copying the geodatabase schema of an ArcGIS data model template

Copying geodatabases

  • Overview of copying geodatabases
  • Copying a geodatabase using the Copy tool
  • Copy a geodatabase using geodatabase XML workspaces
  • Copying a geodatabase using the Extract Data wizard in ArcMap
  • Copying feature classes using Export

Geodatabase migration

  • Migrating to the file geodatabase
  • Migrating to high precision
  • Migrating data from a newer geodatabase release to an older one

Defining the properties of data in a geodatabase

  • An overview and definition of geodatabase data properties
  • Enterprise geodatabase size and name limits
  • Geodatabase table properties
  • Spatial indexes
  • Spatial references in geodatabases
  • Configuration keywords in geodatabases
  • Domains

Adding datasets and other geodatabase elements

  • An overview of adding datasets to the geodatabase
  • Creating new datasets in the Catalog tree
  • Copying feature datasets, classes, and tables to another geodatabase
  • ArcGIS functionality available for tables that are not registered with the geodatabase
  • Register a table or view with the geodatabase
  • Exporting data
  • Loading data
  • Importing data

Data maintenance and transactions

  • An overview of data maintenance and transactions
  • What is a transaction?
  • Transactions and geographic data
  • Data maintenance strategies
  • Deciding how to register data
  • Grant and revoke dataset privileges
  • Update statistics on a dataset using the Analyze Datasets tool
  • Rebuild dataset indexes using the Rebuild Indexes tool
  • Viewing dataset or version locks

Working with nonversioned data

  • A quick tour of working with nonversioned data
  • Configuring an ArcMap edit session to perform nonversioned edits
  • Concurrency and locking
  • Working with data integrity features
  • Editing nonversioned data with constraints
  • Nonversioned editing with the feature cache

Working with versioned data

  • What is a version?
  • An overview of traditional versioning
  • Versioning vocabulary
  • Version scenarios
  • Registering and unregistering data as versioned
  • Managing geodatabase versions
  • Editing versions
  • Compressing a versioned geodatabase

Managing distributed data

  • Understanding distributed data
  • Scenarios using distributed data
  • Working with geodatabase replication
  • Replicas and geodatabases
  • Replication types
  • Connected and disconnected replication
  • Preparing data for replication
  • Replica creation and versioning
  • Replication and related data
  • Replication and topology
  • Replication and geometric networks
  • Replication and raster data
  • Replication and terrains, network datasets, parcel fabrics, and representations
  • Geodatabase replication and ArcGIS Server
  • Creating replicas
  • Synchronization
  • Applying schema changes
  • Managing replicas

Archiving data

  • Geodatabase archiving
  • Enabling archiving
  • The archive process
  • Working with historical versions
  • Working with historical markers
  • Working with the Geodatabase History Viewer
  • Working directly with the archive class
  • Schema changes and archiving
  • Disabling archiving
  • Archiving scenarios

Design tips

This ArcGIS 10.6 documentation has been archived and is no longer updated. Content and links may be outdated. See the latest documentation.

Geodatabase data models are designed to be used in practical application scenarios by a wide range of users. To ensure that each design is easy to understand and implement, each data model was built to support easy migration from existing data structures and has been designed to be flexible, extensible, and easily adapted by your organization. Here are a few final design tips to help you with your design implementation:

  • Build on your existing GIS designs.

    Most existing database designs are suitable for moving forward. You can build on what has worked in the past and find new geodatabase capabilities that will improve on your past efforts.

  • Use generic geodatabase types whenever feasible.

    Combining generic data structures with very rich GIS tools provides the best solutions that will scale and support multiple users and applications. Leverage the ArcGIS software logic as much as possible for your work. Only use customized GIS data structures as a last resort.

  • Integrate related feature classes using topology.

    Legacy ArcGIS Desktop Advanced users with coverages will find many opportunities to integrate feature classes using topologies in the geodatabase. Learn how to use geodatabase topology and its rules. This will create real savings during editing, minimize the amount of customization work you'll need, and increase user productivity. Even small GIS organizations will see up to a 40 percent increase in efficiency for data maintenance.

  • Combine GIS design concepts from this section with traditional relational database design methods.

    Both database management system (DBMS) and GIS design methodologies are critical for good GIS design. One is not sufficient without the other. Learn to use and apply both sets of techniques.

  • Prototype and pilot your geodatabase design.

    Prototyping a design with ArcGIS Desktop using a file or personal geodatabase, or a geodatabase for SQL Server express, is easy, fun, and effective. You’ll be surprised at how much insight you’ll gain through experimentation and how much more effective and efficient your design process will become.

During the final stage of design, you’ll want to test scalability and workflows that represent the work that your organization will perform with your geodatabase. Use this to make final adjustments to your design. Be practical in your final test phase and adjust your design as necessary.

ArcGIS Desktop

  • Home
  • ArcGIS Pro
  • ArcMap
  • Documentation
  • Support

ArcGIS

  • ArcGIS Online
  • ArcGIS Desktop
  • ArcGIS Enterprise
  • ArcGIS
  • ArcGIS Developer
  • ArcGIS Solutions
  • ArcGIS Marketplace

About Esri

  • About Us
  • Careers
  • Esri Blog
  • User Conference
  • Developer Summit
Esri
Copyright © 2021 Esri. | Privacy | Legal