Archives of the TeradataForum
Message Posted: Fri, 14 Feb 2003 @ 12:16:23 GMT
The columns CREATETIMESTAMP and LASTALTERTIMESTAMP in the various DBC tables were added with Release V2R3, but the feature was not immediately implemented and the columns were populated with a NULL.
I don't remember when I first noticed that the columns were being populated with an actual value, but it was during the V2R4 timeframe. A NULL in CREATETIMESTAMP indicates that the object was created prior to the implementation of the feature.
Although the column LASTACCESSTIMESTAMP has been added to the various DBC tables, it hasn't been implemented yet and will be populated with a NULL. I think that I heard that it's supposed to be implemented in a future release of V2R5.
Another column of a similar ilk is column CREATEUID in the various DBC tables. If the object was created prior to the implementation of the feature (V2R4?), then it will contain a NULL. There are cases where it might contain a hexadecimal 0 and that seems to indicate that the object was created on another machine, archived and then copied to the current machine.
The same seems to be true of column LASTERUID.
With these last two columns, referential integrity isn't maintained (ie- the user who created/altered an object may no longer be an employee).
|Copyright 2016 - All Rights Reserved|
|Last Modified: 27 Dec 2016|