(UPDATED)
How do you pick the number of sessions to assign to your utility jobs? Chances are you guess. In Teradata 13.10 the task of deciding the number of sessions has been moved inside the database, meaning one less thing for you to worry about. Read on for a quick intoduction to how this feature works. Once you get on Teradata 13.10, if TASM is enabled, then the database is dictating the number of sessions each load job will get. This is happening automatically, without your doing a thing. Any parameters or config files you have set up will be ignored, and by default you will get a number of sessions between 20 and 100 for each utility you run. (See the new text in the section titled "Is the Session Setting a Max or a Limit?" if you have read this posting previously.)
The number of sessions specified by the session management default rules will be different based on the number of AMPs in your configuration, as illustrated by the following formulas. First is the formula that the default session management rules use for the load type utilities:
FastExport always uses 1 session per AMP, up to an upper limit of 4 sessions per job. Here is the formula that the default session management rules use to determine the number sessions for archive and restore jobs:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
sleep 1; tenacity 1; .SET SESSION CHARSET "ASCII"; .RUN NODEID.user1; set record VARTEXT "|" DISPLAY_ERRORS NOSTOP; errlimit 3; SET QUERY_BAND = 'UtilityDataSize=SMALL;' UPDATE for session; DELETE FROM fl_table_1; define start_datetime (varchar(200),NULLIF='') ... ,file=data1; begin loading fl_table_1 errorfiles et_fl_table_1, uv_fl_table_1; insert into fl_table_1 ( start_datetime ... ) values ( :start_datetime ... ); end loading; .logoff;
The session management rule that the utility classifies to has a specific number of sessions. There are three versions of each default rule, one for SMALL, one for medium data sizes called "Default", and one for LARGE data sizes. The default version represents the standard number of sessions for that utility and will be used if no query band is passed. If the query band says LARGE it will match to the LARGE version of the rule, whose number of sessions will have been increased by 50%. If the query band says SMALL the rule it matches to will have a number of sessions that will be half of those in the default. An example of those different size-specific rules whose default specifies 32 sessions follows: DEFAULT: LARGE: SMALL: = 32 sessions 32 * 1.50 = 48 sessions 32 * 0.5 = 16 sessions