Logging Pool Sessions on to the Database System | Teradata Director Program - Logging Pool Sessions on to the Database System - Teradata Director Program

Teradata® Director Program Reference - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Director Program
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-11-17
dita:mapPath
cki1641301536147.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
frc1470439950465
Product Category
Teradata Tools and Utilities

The sessions in a pool are logged on to the database once using the START POOL operator command (see START POOL) and remain logged on until they are explicitly logged off by the STOP POOL (or STOP POOL and LOGOFF POOL) operator commands.

When a pool is first established, all pool sessions are not in use. When an application sends a logon request whose logon string matches that of the session pool, the application is assigned an available session from the pool. This results in a “quick” logon, because the application’s logon request does not have to be sent to the database.

The session assigned to the application is marked “in use” and cannot be reassigned to another application until the current application logs off. The logoff returns the session to the pool, where it becomes available for use by another application.