Archives of the TeradataForum
Message Posted: Mon, 25 Jun 2001 @ 17:37:23 GMT
There is no 'native' functionality or parameter setting which will achieve this. This area isn't too good within Teradata.
It can always be coded within an application, but if you're using a tool then that's no good either.
You can write a management application to report on such circumstances and maybe even force the sessions off the system, but that's after the fact - and you may not be able to identify which sessions to force off !
The client side has built-in limits, I think the windows cli only allows a maximum of 20 sessions to be logged on concurrently (I'm not completely certain of this so if anyone else knows better feel free to correct me). The hardware has limits based on number of PEs and number of nodes but those apply to all userids and not to individual userids so are probably not appropriate for what you want to do.
Which of course then begs the question. What are you trying to achieve?
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|