Pitney Bowes MapMarker USA - Manual (Page 197)

Chapter 8:
Additional Considerations for Remote Table Geocoding
MapMarker USA 25
197
User Guide
If MapMarker attempts to lock a row that is already locked, MapMarker follows the default behavior
of the database. Usually this means waiting until that row is released. MapMarker does not use any
deadlock detection beyond that provided by the database.
L
You are responsible for maintaining the relationship of the street address and the
latitude/longitude for that address. For example, whenever you change any street address
information, you must re-geocode that record.
If rows are deleted from your table after MapMarker opens the table, MapMarker reports an error
when it tries to geocode that deleted row.
Remote Database Views
You may only geocode views of a remote table when you are doing a table-to-table geocode. See
Writing Geocoding Output to Another Table on page 191 , for more information.
Rollback Segment Limit
Be sure that you set your database rollback segment or temp space to be sufficiently large enough
to accommodate the size of your database.
Supported Unique Index and Primary Key Data Types by Database
The following table identifies the supported data types by RDBMS. A Primary Key must also be
defined for your table.
If MapMarker encounters a mappable table with a spatial type it does not support, an error message
is displayed and the table is not geocoded.
For a list of ODBC databases supported by MapMarker (including Microsoft Access, Oracle, and
SQL Server) see your product-specific MapMarker Release Notes.
Microsoft SQLServer Microsoft Access Oracle
Char Character Character
Float Number (double) Number
Integer Number (Long Integer) Varchar
SmallInt Number (Integer) Varchar2
Tinyint Number (Single) N/A
Real N/A N/A
Varchar N/A N/A