Create Backdrop Database

For the field unit, the backdrop geodatabase is a personal or file geodatabase that provides a "snapshot" of the data as it exists on the enterprise geodatabase. The backdrop does not have to contain all the features in your Enterprise geodatabase, but rather would be a subset that includes only the features necessary to field users. For example, the data may be subdivided into service areas in which each field user works. Reducing the number of tables and feature classes in the backdrop to only the necessary minimum improves performance.

IMPORTANT: Engine Mobile does not support any relationship involving a non-ArcFM (or non-Designer) object in the Backdrop database.

The following steps describe how to create your backdrop geodatabase. Use Geodatabase Replication (discussed later) to maintain the backdrop geodatabase.

NOTE: To view Feeder Manager 2.0 data in the geodatabase backdrop, after creating the backdrop, ensure you have Feeder Manager 2.0 enabled in ArcCatalog.

File Geodatabases: If you wish to use a file geodatabase in the field, note that this database cannot be compressed because the field user is editing it directly. Geodatabase Replication offers some options:

  • Don't compress the file geodatabase on the server. An uncompressed file geodatabase is larger and can take longer to download to the client, but additional time is NOT required to uncompress on the client.

  • Compress on the server and uncompress on the client. The compressed file geodatabase will take less time to download to the client and use less bandwidth. However, additional time is required to uncompress the file geodatabase once it's on the client machine.

Access Geodatabase: Although the Access database size limit is 2GB, ESRI recommends limiting your Access database size to 500MB or less to ensure effective performance and stability.

QR code for this page

Was this helpful?