Teradata¶

Compatibility¶

The GeoServer Teradata extension is compatible with GeoServer 2.1.1 and higher. GeoServer can connect to Teradata databases version 12.0 or higher. Version 12.0 of the Teradata Database requires the optional geospatial extension to be installed.

Read/write access¶

The Teradata datastore in GeoServer supports full transactional capabilities, including feature creation, editing, and deleting.

To support editing, a table must have one of the following:

• a primary key
• a unique primary index
• an identity (sequential) column

Query Banding¶

The GeoServer Teradata extension supports Query Banding. Query Banding is a feature which allows any application to associate context information with each query it issues to the database. In practice this can be used for purposes of workload management (i.e. request prioritization), debugging, and logging.

GeoServer sends the following information as part of a standard request:

• Name of application (i.e. GeoServer)
• Authenticated username (if set up)
• Hostname (if available)
• Type of statement (i.e. “SELECT”, “INSERT”, “DELETE”)

It is not possible to modify this information from within GeoServer.

Spatial indexes¶

GeoServer will read from a spatial index if its exists. The convention for a spatial index table name is:

[TABLENAME]_[GEOMETRYCOLUMN]_idx

So for a layer called “STATES” with a geometry column called “GEOM”, the index table should be called STATES_GEOM_idx.

This index table should contain two columns:

• A column that maps to the primary key of the spatial data table
• The tessellation cell ID (cellid)

The tessellation cell ID is the ID of the cell where that feature is contained.

Geometry column¶

As per the SQL/MM standard, in order to make a Teradata table spatially enabled, an entry needs to be created for that table in the geometry_columns table. This table is stored, like all other spatially-related tables, in the SYSSPATIAL database.

Tessellation¶

Tessellation is the name of Teradata’s spatial index. In order to activate tessellation for a given layer, an entry (row) needs to be placed in the SYSSPATIAL.tessellation table. This table should have the following schema:

Installing the Teradata extension¶

Teradata database support is not enabled by default and requires the GeoServer Teradata extension to be installed prior to use. In addition to this extension, an additional artifact will need to be downloaded from the Teradata website.

Adding a Teradata datastore¶

Once the extension has been added, it will now be possible to load an existing Teradata database as a store in GeoServer. In the Web Administration Interface, click on Stores then go to Add a new Store. You will see a option, under Vector Data Stores, for Teradata. Select this option.

Teradata in the list of readable stores

On the next screen, enter in the details on how to connect to the Teradata database. You will need to include the following information:

When finished, click Save.

Adding a Teradata store

Using JNDI¶

GeoServer can also connect to a Teradata database using JNDI (Java Naming and Directory Interface).

To begin, in the Web Administration Interface, click on Stores then go to Add a new Store. You will see a option, under Vector Data Stores, for Teradata (JNDI). Select this option.

Teradata (JNDI) in the list of readable stores

On the next screen, enter in the details on how to connect to the Teradata database. You will need to include the following information:

Option	Description
Workspace	Name of the workspace to contain the database. This will also be the prefix of any layers server from tables in the database.
Data Source Name	Name of the database in GeoServer. This can be different from the name of the Teradata database, if desired.
Description	Description of the database/store.
Enabled	Enables the store. If disabled, no layers from the database will be served.
jndiReferenceName	JNDI path to the database.
schema	Schema for the above database.
namespace	Namespace to be associated with the database. This field is altered by changing the workspace name.
Expose primary keys	Exposes primary key as a standard attribute.
Primary key metadata table	Name of primary key metadata table to use if unable to determine the primary key of a table.
Loose bbox	If checked, performs only the primary filter on the bounding box.

When finished, click Save.

Adding a Teradata store with JNDI

Adding layers¶

One the store has been loaded into GeoServer, the process for loading data layers from database tables is the same as any other database source. Please see the Layers section for more information.