Re: TimeStamp Problem

Keeping in mind that the space shown in DSPPFM is not really how much
space is taken up by date, time, timestamp columns and that IBM wrote
DSPPFM and can then get it to format the output anyway they want to. I
think they show it expanded just to ease those using earlier flavors of
RPG and stuff.

So let's try this:

CREATE TABLE ROB.BUZZ06 (

TIMESTAMPCOL06 TIMESTAMP (06)
)
Table BUZZ06 created in ROB.

CREATE TABLE ROB.BUZZ12 (

TIMESTAMPCOL12 TIMESTAMP (12)
)
Table BUZZ12 created in ROB.

INSERT INTO ROB.BUZZ06 (TIMESTAMPCOL06) VALUES(current_timestamp)

1 rows inserted in BUZZ06 in ROB.

INSERT INTO ROB.BUZZ12 (TIMESTAMPCOL12) VALUES(current_timestamp)

1 rows inserted in BUZZ12 in ROB.

for x=1 to 100000;
exec sql INSERT INTO BUZZ06 (TIMESTAMPCOL06) VALUES(
current_timestamp);
exec sql INSERT INTO BUZZ12 (TIMESTAMPCOL12) VALUES(
current_timestamp);
ENDFOR;

DSPOBJD
buzz06
Storage information:
Size . . . . . . . . . . . . . . . . : 1359872
buzz12
Storage information:
Size . . . . . . . . . . . . . . . . : 1622016
A difference of 262,144 bytes.
/ 100,001 rows
= 2 bytes per row

Used disk drives go for about $1/GB
http://www.ebay.com/itm/IBM-4326-9406-35GB-15K-Disk-Drive-/171104244067
http://www.ebay.com/itm/IBM-9406-4319-35GB-DISK-DRIVE-FOR-AS400-z7-/351114316190?pt=US_Internal_Hard_Disk_Drives&hash=item51c00b499e

So those extra 2 bytes just ate up about $0.000262 amount of disk space. I
can see where you may need to fill a room full of executives and debate on
this for a few hours before spending that amount.


Rob Berendt