Fragment by Expression, Remainder dbspace

One quick question about fragmenting by expression, but first some background information. IDS 7.31 HP/UX 11.0 Table to Fragment has 200 Million Rows and each row is 1006 Bytes (Not my fault!) I am planning on fragmenting the above table accross 12 dbspaces based on a CHAR(1) field that is populated with a value that represents what dbspace the row should be inserted into. What I would like to know is if I had a 13th dbspace reserved for REMAINDER to avoid an error if the CHAR(1) field was not populated or populated incorrectly; how much can this effect performance. The REMAINDER dbspace would have few to no records. Thanks for any info. Andrew Sent via Deja.com http://www.deja.com/ Before you buy.

aford6875@my-deja.com wrote: > > One quick question about fragmenting by > expression, but first some background information. > > IDS 7.31 > HP/UX 11.0 > Table to Fragment has 200 Million Rows and each > row is 1006 Bytes (Not my fault!) WOW exactly 1/2 a page. Someone had to work on that one! > I am planning on fragmenting the above table > accross 12 dbspaces based on a CHAR(1) field that > is populated with a value that represents what > dbspace the row should be inserted into. > > What I would like to know is if I had a 13th > dbspace reserved for REMAINDER to avoid an error > if the CHAR(1) field was not populated or > populated incorrectly; how much can this effect > performance. > > The REMAINDER dbspace would have few to no > records. It should have little effect as long as you have stats updated on that column. Art S. Kagel