DB2, VARCHAR, LONG VARCHAR

VARCHAR, LONG VARCHAR

Author	Message
ayan.. #1 / 4	VARCHAR, LONG VARCHAR Hi, Dumb question: In DB2 7.1, if a VARCHAR can contain up to 32,672 bytes, and a LONG VARCHAR contains up to 32,700 bytes - what determines which kind of varchar should be used (apart from an extra 28 bytes?) Thanks, Sent via Deja.com http://www.***.com/ Before you buy.
Mon, 28 Apr 2003 03:00:00 GMT

Blair Kenneth Adamach #2 / 4	VARCHAR, LONG VARCHAR Always use a varchar if possible. Long fields have extra processing that can hurt performance. (Actually, another long field - CLOB - is a better choice than LONG VARCHAR if you can't use a VARCHAR). To use 32K varchars, you need a tablespace and bufferpool defined with a 32K page size. Quote: > Hi, > Dumb question: > In DB2 7.1, if a VARCHAR can contain up to 32,672 bytes, and a LONG > VARCHAR contains up to 32,700 bytes - what determines which kind of > varchar should be used (apart from an extra 28 bytes?) > Thanks, > Sent via Deja.com http://www.deja.com/ > Before you buy.
Mon, 28 Apr 2003 03:00:00 GMT

ayan.. #3 / 4	VARCHAR, LONG VARCHAR Quote: > Always use a varchar if possible. Long fields have extra processing > that can hurt performance. (Actually, another long field - CLOB - is > a better choice than LONG VARCHAR if you can't use a VARCHAR). > To use 32K varchars, you need a tablespace and bufferpool defined > with a 32K page size. What does this do to my table if I have other fields defined in the row? Say, a row that has BIGINT, SMALLINT, SMALLINT, VARCHAR(32K)? Also, would you happen to know if the DB2 Net Search Extender works with CLOB fields? Thanks for your response. Regards, Sent via Deja.com http://www.deja.com/ Before you buy.
Mon, 28 Apr 2003 03:00:00 GMT

Blair Kenneth Adamach #4 / 4	VARCHAR, LONG VARCHAR Net.Search is designed to work with CLOBs. If you have other columns in the table, each has a length that reduces the maximum size possible for the varchar. A 32K page allows a maximum row width of 32677. You calculate row width by summing the widths of all non-long field columns. Quote: > > Always use a varchar if possible. Long fields have extra processing > > that can hurt performance. (Actually, another long field - CLOB - is > > a better choice than LONG VARCHAR if you can't use a VARCHAR). > > To use 32K varchars, you need a tablespace and bufferpool defined > > with a 32K page size. > What does this do to my table if I have other fields defined in the row? > Say, a row that has BIGINT, SMALLINT, SMALLINT, VARCHAR(32K)? > Also, would you happen to know if the DB2 Net Search Extender works > with CLOB fields? > Thanks for your response. > Regards, > Sent via Deja.com http://www.deja.com/ > Before you buy.
Tue, 29 Apr 2003 03:00:00 GMT

Page 1 of 1

[ 4 post ]