 |
 |
Archives of the TeradataForum
Message Posted: Fri, 04 Feb 2011 @ 14:01:23 GMT
Subj: | | Re: Diffrence between dbc.accesslog and dbc.logonoff |
|
From: | | Victor Sokovin |
| In the otherhand, when dbc.logonoff is locked by a query [ delete from dbc.logonoff], a logon action was waiting until the lock was
released. | |
| Why is there a differrence across the two cases? | |
Logon procedure is not just about inserting a record in dbc.logonoff. There can be a totally different logic than that of a simple SQL
deadlock. No reason to expect the same behavior here.
Victor
| |