How "SARP_TRACK_PLAN" table used in Sagent repository
Product Feature: Administration
The Sagent repository tables SARP_TRACK_USER, SARP_TRACK_PLAN, SARP_TRACK_STEP, and SARP_TRACK_TABLE are used to maintain user information.
These four tables are linked by a SessionId that is generated when a user logs into Sagent Data Flow.
Each user login is treated as a unique session and a unique SessionId is associated with it.
The SARP_TRACK_USER table contains user information such as,
The SARP_TRACK_STEP table contains information on all the steps pertaining to the plans that were executed in a particular user session.
The SARP_TRACK_TABLE table contains information on the BaseViews and the databases, corresponding to each step, which were accessed when a plan was executed.
These four tables are linked by a SessionId that is generated when a user logs into Sagent Data Flow.
Each user login is treated as a unique session and a unique SessionId is associated with it.
The SARP_TRACK_USER table contains user information such as,
- User name with which the user logged in.
- Client application’s name specifying the Sagent client through which the user logged in.
- The time when the user logged in.
- The time when the user logged out.
The SARP_TRACK_STEP table contains information on all the steps pertaining to the plans that were executed in a particular user session.
The SARP_TRACK_TABLE table contains information on the BaseViews and the databases, corresponding to each step, which were accessed when a plan was executed.
UPDATED:
December 6, 2017
