Not 100% sure, but I believe that option 2 still retains the extra null byte in the row, and does the normal null indicator processing for it (in the database engine and the application program), and then checks whether the null indicator is set to null. Processing is probably more expensive for option 2, but maybe not measurable.
In theory, disk storage and memory is more expensive for option 2 because of the null indicator byte. However, having just one column in a table with an extra byte may not decrease the number of rows that fit on a page, so it might not have any practical effect on disk or memory.
Last edited by Marcus_A; 06-12-04 at 18:53.
M. A. Feldman
IBM Certified DBA on DB2 for Linux, UNIX, and Windows
IBM Certified DBA on DB2 for z/OS and OS/390