Archives of the TeradataForum
Message Posted: Tue, 13 Jan 2004 @ 18:02:15 GMT
Consider structuring your userids in a manner that lends itself to having multiple control points. Some Teradata administrators prefer having one userid per application group. This gives the administration staff the ability to differently manage different applications. What is proper management for one application may not be proper for any other application.
When looking strictly at the userid, one sees, from a DBMS perspective, regulation of access rights, spool/temp/perm space, all the stuff you see in "create user".
Next take a look at TDQM administration and workload management, you will see the ability to regulate based on explain plan time, spool and concurrency. Most interesting is the time limit which is very effective at recognizing and expediting short queries.
So should you see the value in having different regulation points, then my recommendation is to have multiple userids to gain those mechanisms.
Clearly this is a tough question . . . which is the best way to go? Caution would lend credibility to having multiple userids but exact reasons may only surface later with more experience.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|