About Excluding Objects from Map Reassignments - Teradata Database - Teradata Vantage NewSQL Engine

Teradata Vantage™ - Database Administration

Product
Teradata Database
Teradata Vantage NewSQL Engine
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2019-05-03
dita:mapPath
tgx1512080410608.ditamap
dita:ditavalPath
TD_DBS_16_20_Update1.ditaval
dita:id
ujp1472240543947
Product Category
Software
Teradata Vantage
To exclude tables, join indexes, or hash indexes from the list to analyze and reassign to different maps, use procedures to create an empty list of exclusions and then add objects to it. In the following example, a DBA creates an exclusion list named 'MyExclusions' consisting of all tables in database 'Payroll', an individual table 'Employee.Withholding', and all tables in database 'Taxes' whose names begin with 'Rate'.
CALL TDMaps.CreateExclusionListSP('MyExclusions', NULL, :ExclusionListId);
CALL TDMaps.AddExclusionListEntrySP('MyExclusions', 'Payroll', NULL,:NumObjectsAdded);
CALL TDMaps.AddExclusionListEntrySP('MyExclusions', 'Employee', 'Withholding',:NumObjectsAdded);
CALL TDMaps.AddExclusionListEntrySP('MyExclusions', 'Taxes', 'Rate%', :NumObjectsAdded);

The result is that these tables are marked as exclude in the ActionsTbl and will not be considered for redistribution to other AMPs. The list of excluded objects is visible in the view TDMaps.ExclusionLists[V][X].

For more information on these procedures, including the syntax, see Teradata Vantage™ SQL Operators and User-Defined Functions, B035-1210.