This feature allows Teradata Database to use multiple maps for table and join index data distribution. A map can include all AMPs in the system or a subset of AMPs to which the table and join index rows will be distributed. Every table and join index is assigned to use a map, either explicitly in a CREATE/ALTER statement, or by default by Teradata Database.
The MAPS Manager portlet in Teradata Viewpoint can facilitate analyzing map use and moving database objects among maps
- Provides high data availability across the analytical ecosystem. Dramatically reduces the required maintenance window for system reconfiguration and data redistribution after a system expansion.
- More efficient distribution of data, and optimal use of resources by associating small tables with small (one-AMP or few-AMP) “sparse” maps.
- Teradata Database includes two sparse maps, and users with appropriate privileges can create additional sparse maps if needed.
- New tables, views, and procedures are provided to aid in managing multiple maps and migrate tables to new maps after system expansion with minimal impact on system availability.
- More consistent tactical query performance with higher query concurrency.
- You can associate maps with table operators and foreign servers to ensure the operator function code is stored and run only on AMPs that store data for tables on which the operators run.
- The Teradata MAPS feature introduces a new database, TDMaps, installed by DIP, that owns new tables, views, and procedures that aid in the management of maps.
- Privileges on TDMaps must be granted to map administrators.
- MAPS is disabled by default on systems that are upgraded from pre-16.10 versions of Teradata Database. After MAPS has been enabled, the system cannot be backed down to an earlier release. MAPS is enabled by default on systems that have been sysinited on or migrated to Teradata Database 16.10.
- The Teradata MAPS feature introduces a new dedicated fallback scheme, used for all tables that use maps created on Teradata Database 16.10.
- The Teradata MAPS Architecture feature is not compatible with the ARC (arcmain) archive/recovery utility. If MAPS is enabled, you should use Teradata Data Stream Architecture (DSA) for archive/recovery operations. For more information on DSA, see Teradata® Data Stream Architecture User Guide, B035-3150.
- CREATE MAP, DROP MAP, SHOW MAP
- GRANT MAP, REVOKE MAP
- CREATE TABLE, CREATE TABLE AS, ALTER TABLE
- CREATE JOIN INDEX, ALTER JOIN INDEX
- CREATE HASH INDEX, ALTER HASH INDEX
- CREATE DATABASE, CREATE USER, MODIFY DATABASE, MODIFY USER
- CREATE PROFILE, MODIFY PROFILE
- CREATE FUNCTION, REPLACE FUNCTION
- CREATE FOREIGN SERVER, MODIFY FOREIGN SERVER
- EXPLAIN [IN XML]
- HELP SESSION
- SHOW [IN XML] TABLE
- SHOW [IN XML] JOIN INDEX
- HASHAMP, HASHBACKAMP
- CreateMapListSP, AddMapListEntrySP, and AddMapListEntrySPX
- CreateObjectListSP, AddObjectListEntrySP, and AddObjectListEntrySPX
- CreateExclusionListSP, AddExclusionListEntrySP, and AddExclusionListEntrySPX
|Maps||Teradata® Database Design, B035-1094|
|Creating maps and associating maps with tables||Teradata® Database SQL Data Definition Language - Syntax and Examples, B035-1144|
|Associating maps with table operators and foreign servers||The EXECUTE MAP clause in Teradata® Database SQL Data Definition Language - Syntax and Examples, B035-1144|
|Managing maps||Teradata® Database Administration, B035-1093|
|MAPS Manager portlet in Teradata Viewpoint||Teradata® Viewpoint User Guide, B035-2206|
|Syntax for new SQL procedures and macros||Teradata® Database SQL Functions, Operators, Expressions, and Predicates, B035-1145|
|Configuration and Reconfiguration utilities||Support Utilities , B035-1180|