MAPS Manager Overview - Teradata Viewpoint - Teradata Workload Management

Teradata® Viewpoint User Guide

Product
Teradata Viewpoint
Teradata Workload Management
Release Number
17.10
Published
February 2022
Language
English (United States)
Last Update
2022-06-28
dita:mapPath
lks1628075605455.ditamap
dita:ditavalPath
tky1501004671670.ditaval
dita:id
B035-2206
lifecycle
previous
Product Category
Analytical Ecosystem

The MAPS Manager portlet allows you to incrementally redistribute data from tables across new AMPs after a system expansion instead of taking a system offline for an extended time. You can also actively monitor systems and provide recommendations to make sure objects are in optimal maps. Using appropriately sized maps increases parallelism and speed when accessing objects and provides greater efficiency for smaller objects.

MAPS Manager manages the following objects:
  • Tables
  • Hash indexes
  • Join indexes

The portlet provides two methods to move objects to a new map. Both methods allow you to improve system performance without extended downtime. You can also view all maps defined on the system and to add sparse maps as needed.

System Monitoring
System Monitoring provides ongoing recommendations to optimize the location of objects. You can accept recommendations and schedule moves when convenient.
Object Workflows

Object workflows let you create ad-hoc workflows where you can select which objects to move and the order and time to move the objects.

Maps
Maps shows all available contiguous and sparse maps on the system. It also identifies the system default contiguous map and its sparse maps that are used for analysis.

You can also grant and revoke permissions for the maps on your system.

If JWT integration with Vantage is enabled (versions 16.50.05.00 and later), you will not be prompted to log in. A Disconnect option is available, which will allow the user to login using different credentials.

Note that once disconnected, the user will continue to be prompted to enter credentials. This setting is saved per portlet instance; a new portlet instance will bypass the login dialog.