Geodatabases: types, users/privileges

management

May 2017
Spatial Data Infrastructure

• A spatial data infrastructure (SDI) is a framework of

spatial data, metadata, users and tools that are
interactively connected in order to use spatial data in
an efficient and flexible way;
• data and metadata should not be managed in a
distributed way;
• good coordination between all the actors is necessary
and the definition of standards is very important.
Geographic information

Geodata is information about geographic locations that is stored in a format

that can be used with a geographic information system (GIS).

It can be stored in several formats and storage systems:

 Database
 Geodatabase
 Shapefile
 Coverage
 Raster image
 DBF table or Microsoft Excel spreadsheet
 etc.
Database and geodatabase

A database is an organized collection of data

A geodatabase is a database, in which some of the content is spatially

enabled.

Geodatabases have a comprehensive information model for representing

and managing geographic information.

ArcGIS geodatabase is a collection of geographic datasets of various types

held in:
• a common file system folder (File Geodatabase)
• a Microsoft Access database (Personal Geodatabase)
• a multiuser relational DBMS, such as Microsoft SQL Server, PostgreSQL
and several others (Enterprise Geodatabase)
How an ESRI geodatabase works?

At the core of the geodatabase is a standard relational database schema.

Within the geodatabase, there are two primary sets of tables:

• system tables - the geodatabase system tables keep track of the contents of
each geodatabase. They essentially describe the geodatabase schema that
specifies all dataset definitions, rules, and relationships.

• dataset tables - each dataset in the geodatabase is stored in one or more tables.
The dataset tables work with the system tables to manage data

© ESRI, 2014
 ESRI Geodatabase types and comparison

Personal File ArcSDE

Key characteristics
geodatabase geodatabase geodatabase
some readers and one many readers or one multiuser
N. of users writer writer per feature dataset

Storage format Microsoft Access file File folder DBMS

2 GB per Access 1 TB for each dataset DBMS limits

database (but
Size limits performance issues if >
500 MB)

Versioning support Check-out

One-way
Check-out
One-way
Full

Windows file system Operating file system Provided by DBMS

Security security security
Windows file system File system management DBMS functions for
Database management backup, recovery,
administration replication, etc.
 ArcSDE Geodatabases types and comparison

Desktop Workgroup Enterprise

Scenario Small or 1 user Small-medium Large scale

Data storage SQL Server Express SQL Server Express SQL Server, Oracle,
Postgres….
Management ArcCatalog ArcCatalog ArcCatalog, ArcSDE
Interface DBMS, command line
Storage Capacity 10 GB 10GB Depends on the server

Number Concurrent 1 editor and 3 10 editors and Unlimited editors and

Users readers readers readers
Network Local Network Intranet and Internet Intranet and Internet
application
Characteristics Versioning Versioning, Multiuser Versioning, Multiuser
editing editing, Enterprise IT
Integration
Geodatabase user data (dataset tables)

All GIS users usually work with three

fundamental dataset types. A set of feature
classes; a number of attribute tables; a large
set of imagery and raster datasets to work
with.  Geometries are stored and managed in
attribute columns along with traditional tabular
attribute fields.

© ESRI, 2014

The geodatabase has a number of additional data elements and dataset types that
can be used to extend this fundamental collection of datasets (e.g. attribute
domains, relationship classes, subtypes, versioning, feature datasets, topology etc.)
Feature class basics

Feature classes are homogeneous collections of

common features, each having the same spatial
representation (points, lines, polygons or
annotations) and a common set of attribute
columns

© ESRI, 2014

Each feature class is managed in a single table. A shape column in each row is used to
hold the geometry or shape of each feature

© ESRI, 2014
Feature datasets

A feature dataset is a collection of feature classes, with common

characteristics with respect to:

• Spatial reference
• Vertical coordinate system
• Geometric tolerance: xy, z, m
• Spatial Resolution: xy, z, m

NOTES:
o Geometric tolerance (in ESRI’s world) is the distance that coordinates are
allowed to be adjusted by the software during various processing
operations
o Spatial resolution (in ESRI’s world) is the numeric precision used to store
the coordinate values. Precision is important for accurate feature
representation, analysis, and mapping.
Feature datasets
Feature datasets
Feature datasets
Feature datasets
Feature datasets
WFP standards for feature datasets

Feature classes can be grouped following the same rule as the

“classes” in layer naming convention.

Therefore the below feature datasets must be created:

• BND (boundaries)
• TRS (transportation)
• HYD (hydrography)
• POI (points of interest)
• POP (population)
• WFP (WFP thematic data)
• PHY (physical)
• CLI (climatology)
• UTI (utilities)
• NHR (natural hazards)
What are user accounts?

User accounts are unique names and passwords used to identify a

person or client application that connects to your database

User accounts perform the following functions:

• Proved a way to control what type of access (if any) a person or
client application has to a database and its datasets
• Determine who owns what data in the database

NOTE: when you create your user accounts and the database roles, do
not use quotation marks or special characters, because they might not
be supported by the underlying database management system.
Groups and users and super users

In a Geodatabase implemented with the PostgreSQL DBMS there are 2

super users:

• Database superuser “postgres”. Used to perform special operations

at database level (save backups, delete the database… Never to be
used by the GIS officer)

• Geodatabase administrator user “sde”. Used to perform special

operations at geodatabase level (create users, run maintenance
tasks, kill locks)
Groups and users and super users

The standard name for a group of users with common permissions in

an ESRI Geodatabase is “role”

In the Spatial Data Infrastructure there are 3 type of roles:

• creator: group of users that can load data into the GeoDatabase,
edit content and use it for all GIS purposes (mapping, analyses,
create web services…);

• editor: group of users that have permissions to access layers loaded

into the Geodatabases by other users with “creator” permissions
and edit it with ArcGIS editing toolbar;

• viewer: group of users that have only permissions to access layers

loaded into the Geodatabases by other users with “creator” …. NO
EDITING;
Database access in ArcGIS

You can connect to databases from ArcGIS to view, query, and analyze the data they
contain.

In order to access to a database, you must create a connection file, specific for the
DBMS you want to access, providing database instance name, authentication type
and credentials, database name

© ESRI, 2014
 Create Users

Users can be created into the GeoDatabase using an ArcToolbox.

1. Start ArcCatalog or ArcMap

2. Open the ArcToolBox.

3. Select Database Management tool

4. Select Geodatabase Administration

5. Launch the Create Database User tool

6. Fill-in information below and click OK to create the user and assign it the right role:

Input Database Connection: Specify the connection file to the enterprise

geodatabase, which is made as a database administrator
(the connection file created with sde user)
Database User: “Type the name you want to give to the user”
Database User Password: “Type the password you want to assign to the user
Role: “type the name of the group to which you want to associate the user
(creator, editor or viewer)
 Grant and Revoke privileges to users

If you want to let other database users view or modify the contents of any data in a
database, you must grant them the privileges to do so.

You can grant just select privileges, meaning the user can read and select from but not
modify the contents of a dataset. You can also grant update, insert, and delete privileges,
which allow the user to modify the contents of a dataset.

To grant and revoke privileges in the GeoDatabase you can use the Privileges Dialag Box

NOTE: You must be the owner of that dataset to modify privileges

1. Connect to the GeoDatabase that contains the data you own and
for which you want to grant or revoke privileges.

2. Right-click the Feature class, Feature Dataset or Raster Dataset or

Table, point to Manage, and click Privileges. The Privileges dialog
box opens.

3. If the user or role whose privileges you want to change is already

in the list, check or uncheck the boxes for the privileges you want
to grant or revoke, and then click OK to apply your change

4. If the user or role is not already in the list, do the following: Click
Add to open the User/Role dialog box.
 Grant and Revoke privileges to users

5. You can choose the database users or roles you want to add from the list by checking the
box next to their names;

6. Click OK to close the User/Role dialog box.

7. Check the boxes of the privileges you want each new user or role to have and click OK.
Geodatabase maintenance

Geodatabase main maintenance tasks include:

• Locks management – GeoDatabases use locks system to prevent users to modify

feature classes structure while other users are using them.
• Database backup and recovery - The data stored in your geodatabase must be
protected from loss or corruption
• Update statistics - As the data and components within the geodatabase change,
table and index statistics become outdated. This is a problem because the
database uses the statistics to process queries from users or client applications.
For this reason, database statistics must be updated periodically
• Compress versioned geodatabases - As edits are made to versioned
geodatabases, the number of states and rows in the delta tables grows, slowing
database performance
• Synchronize replicated data with parent geodatabase
• Upgrading the geodatabase - To take advantage of new functionality, you will
periodically need to upgrade your software by either installing a newer version
or installing a service pack or patch
 Locks management

Most of the GeoDatabase maintenance tasks will be performed automatically by scripts that will be created
during the installation of the Spatial Data Infrastructure.

GeoDatabase administrators must take care only of locks management.

Locks are applied to geodatabase objects to help ensure data integrity.

For example, if someone is editing the data in a table, a schema lock is placed on the table so the owner cannot
change the table's schema while someone is editing the data.

View Connected users

Geodatabase administrators can use the Connections tab on the Geodatabase Administration dialog box to view all users
connected to ArcSDE geo-databases.
1. Start ArcMap or ArcCatalog and connect to the Geodatabase with a
connection file created with the user “sde”.

2. Right-click the database connection in the Catalog tree, point

to Administration, then click Administer Geodatabase.

3. Click the Connections tab.

A list of all user sessions that are currently connected to the

geodatabase is displayed. Your session is displayed in gray, italic text. If
necessary, you can disconnect user sessions by right-clicking a session
and clicking Disconnect User.
 Locks management

In a geodatabase there are two different lock modes, shared locks and exclusive locks.

A shared lock is created on an individual dataset when it is in use; for example, any time a user is editing or
querying the contents of a feature class or table. This mechanism is used so other users cannot change the
schema of a dataset while it is in use.

An exclusive lock is used to lock a dataset in the geodatabase from use by others to make necessary changes to
it, for example, a schema change or even delete the dataset from the geo-database.

View and manage locks

Geodatabase administrators can use the Connections tab on the Geodatabase Administration dialog box to view all users
connected to ArcSDE geo-databases.

1. Start ArcMap or ArcCatalog and connect to the Geodatabase with a

connection file created woith the user “sde”.

2. Right-click the database connection in the Catalog tree, point

to Administration, then click Administer Geodatabase.

3. Click the Locks tab.

A list of locks on all objects in the geodatabase is displayed. You can

disconnect users sessions, thereby dropping the locks held by that
session, by right-clicking a session and clicking Disconnect User.
 Database performance improvement

To maintain database performance, the geodatabase administrator must periodically run a

compress operation to remove unused data.

The frequency with which you need to perform a compress operation is based on the amount
of editing that takes place in your geodatabase. If you have a high volume of edits, you should
probably compress the geodatabase once a day. For average or low edit volumes, you should
compress at least once a week.

Database compression

You can run the database compression through ArcMap or ArcCatalog following the steps below.

1. Connect to your geodatabase using the administrative user (sde)

2. Right-click the database connection in the Catalog tree, point to Administration, then click Compress
Database
3. Click Yes to confirm that you want to run the compression operation on the selected geodatabase.
 Database performance improvement

Database management systems determine the most efficient way to execute the queries sent to them based on
database statistics. Therefore, for optimal performance of datasets created within Enterprise geo-databases, you
need to keep the database statistics current by frequently updating them.

Analyze datasets - update statistics

To open the Analyze Datasets tool from the Catalog tree in ArcCatalog or ArcMap and update dataset statistics,
do the following:

1. Start ArcMap or ArcCatalog;

2. Navigate to the Analyze Datasets geoprocessing
tool in the Geodatabase Administration toolset in
the Data Management toolbox;

3. Use the database connection file created with the

owner of the datasets you want to analyze. (ex.
sudan – NOT THE SDE CONNECTION);

4. From the Datasets to Analyze list, choose the

tables, feature classes, feature datasets, raster
catalogs, raster datasets, or mosaic datasets for
which you want to update statistics.

5. Leave the three checkboxes checked.

6. Click OK to run the tool.

Geodatabases: multiuser functionality

VERSIONING: mechanism that enables the geodatabase to manage and

maintain multiple states while preserving database integrity. It is the basis for
multiple users accessing and editing data simultaneously.

REPLICATION: enables GIS data to be shared across two or more

geodatabases. Data changes can be made in each geodatabase, then
synchronized.
Geodatabases: versioning

VERSIONED EDITING

 Ability to manage conflict resolution

 Supports undo/redo capability
 Supports the full geodatabase model
 Supports geodatabase archiving and replication
 Supports long transactions
 Persistent record of changes

NON-VERSIONED EDITING

 Editing of source data directly

 Last edit is final
 No ability to undo/redo changes
Geodatabases: replication

 Is built on top of the versioning environment

 Supports the full geodatabase data model, including topologies and geometric
networks
 Can work in an asynchronous model (The replication is loosely coupled so that each
replicated geodatabase can work independently and still synchronize changes with
one another.)
 Does not require a uniform DBMS across replicas
 Works in a connected or disconnected environment
 Can utilize local geodatabase connections as well as geodata services (through
ArcGIS for Server) to access the geodatabase over the Internet
Geodatabases: replication

Checkout/Check-in replication: Checkout/Check-in replication allows you to

make edits to the child replica data, then synchronize these changes with the
parent.

Once the data has been synchronized, you can no longer synchronize additional
edits. If additional edits are required, you must create a new checkout replica.

For a checkout replica, the parent must be hosted in ArcSDE while the child can
be hosted in either an ArcSDE, file, or personal geodatabase.
Geodatabases: replication

ONE_WAY REPLICATION: allows data changes to be sent multiple times

from the parent replica to the child replica.

Changes cannot be sent from the child replica to the parent replica. The
parent replica's data is editable, but the data in the child replica is
considered read-only.

One-way replication is only supported between ArcSDE geodatabases.

It requires the data in the parent to be versioned but has an option that
allows the data in the child to be un-versioned.
Geodatabases: replication

TWO_WAYS REPLICATION: allows data changes to be sent multiple times

from the parent replica to the child replica or from the child replica to the
parent replica.

Two-way replication is only supported between ArcSDE geodatabases.

The data must be versioned in both the parent and the child.
Geodatabases: replication

Geodatabase replication is supported on both connected (LAN or WAN) and

disconnected systems.

A disconnected system is one in which the replica geodatabases are not on

the same network.

If disconnected, replica creation and synchronization are accomplished

through workflows involving file transport.

Connected systems involve local connections on a LAN or using ArcGIS

Server for remote access on a WAN.
Geodatabases: basics
Preparing Data for replication

1. The database user must have write access to the data (in case you want
to apply schema changes the user must have loading/creation
privileges);

2. All data must be versioned as fully versioned (it cannot be versioned

with option to move edits to base);

3. Each dataset must have a GLOBALID column;

4. All spatial data must stored in an high precision spatial reference.

Data to be replicated can be filtered by extent, selection or definition

queries.