Pitney Bowes MapMarker USA - Manual (Page 187)

Chapter 8:
Supported Databases
MapMarker USA 25
187
User Guide
Supported Databases
MapMarker USA 25 supports the following ODBC databases and drivers.
• SQL Server
• Microsoft Access
• Oracle
For a list of ODBC databases supported by MapMarker (including Microsoft Access, Oracle, and
SQL Server) see your product-specific MapMarker Release Notes.
The SQL Server and MS Access drivers are installed with MDAC 2.8.
You must install the Oracle driver separately. To use the driver, you must have the Oracle client
installed.
Remote Tables and Spatial Objects
MapMarker supports remote database geocoding via ODBC for relational database management
systems (RDBMS). The RDBMS stores coordinates in X,Y columns. The RDBMS stores the
geocoded spatial object directly.
See the following topics:
Mappable Tables and the MapInfo Map Catalog on page 187
Supported Spatial Index Types on page 187
Mappable Tables and the MapInfo Map Catalog
This section describes the mappable tables and the MapInfo Map Catalog, features that are an
integral part of remote geocoding with MapMarker.
A mappable table is a table of data that has its spatial information recorded in the MapInfo Map
Catalog. Mappable tables are managed by the MapInfo Map Catalog. MapMarker reads the Map
Catalog each time you geocode a remote mappable table to know how to handle the spatial object.
A Map Catalog is optional for X,Y databases. The MapInfo Map Catalog must have an entry for each
table in the database that you wish to geocode.
We recommend that you create your Map Catalog and make a table mappable within MapInfo
Professional. Specific tools and commands are provided there for this purpose.
If, however, you do not have access to MapInfo Professional, you can do these procedures
manually. See
Creating a Map Catalog Manually .
Supported Spatial Index Types
MapMarker supports X,Y (for Oracle, SQL Server, and Microsoft Access). This is shown in the Map
Catalog under the column SPATIALTYPE for X,Y.