Archives of the TeradataForum
Message Posted: Tue, 07 Apr 2015 @ 15:36:24 GMT
We have just started using account strings to all the available users and I have assigned all the priorities to users as directed by our architect. I just modified the user and replaced the accountsrting field with $M,$H,$L respectively.
But this morning I noticed something when I ran these queries:
select unique UserName,AcctString from dbc.qrylog where AcctString = 'dbc' select unique UserName,AcctString from dbc.dbqlogtbl where AcctString not like 'dbc'
Most of the users are present in both of these results.
But when I see the database information of the user it shows the accountstring which I have given to it.
My question is why is it still using the default prority sometimes and the prority which I assigned some times? Did I do something wrong while I was assigning the performance grops.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|