|
Archives of the TeradataForumMessage Posted: Wed, 08 Dec 2004 @ 12:10:40 GMT
Cool, I never noticed this table before. Thanks for teaching me something. By using SYS_CALENDAR.CALENDAR.DAY_OF_CALENDAR and DBC.USERS. PasswordLastModDate, I believe that I proved (I had no differences in my active users) that the following would work: select username, calendar_date from dbc.oldpasswords , sys_calendar.calendar where day_of_calendar = passworddate - 693901 order by 1; The number 693901 is the differnece between a known password change (yesterday) and the Calendar's day of calendar. I may have to play with this a little. Using ROW_NUMBER, you could easily build a nice audit report with the last x number of password changes. It probably wouldn't be real meaningful, unless you could tie it to the dates he logged in. Since he wouldn't have to change the password during periods that he wasn't logging in. You would probably need to take the first login after the next required change (password change + days allowed to use old password) and ensure that he changed his password. I need to think on this one. Thanks again, Glen
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||