When to Choose Daemon-Level Enforcement - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.20
Published
November 2021
Language
English (United States)
Last Update
2021-11-04
dita:mapPath
wph1512683331242.ditamap
dita:ditavalPath
4101_UG_dm_1620.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem
Daemon-level enforcement provides broad permission controls. Data Mover users are granted general read, write, and execute privileges. With daemon-level enforcement, a user who has daemon-level read privilege can view all Data Mover jobs that exist, including jobs the user did not create. This makes permission management very simple, but does not allow for tight control of what users can do. Daemon-level enforcement is recommended in the following cases:
  • Only a few power users are using Data Mover, and all users are trusted with broad control.
  • No need to isolate specific work. All users can have some level of access to all Data Mover work.
  • No need for specific job ownership. All jobs are in one general pool that all users can access at some level.