Figure 106 shows the kind of information that you see when you select the Fragments option for an indexed table created with a round-robin fragmentation strategy.
Idx/Tbl Name Dbspace Type Expression cust dbspace1 T cust dbspace2 T cust rootdbs T cust dbspace1 I cust dbspace2 I cust rootdbs I
Idx/Tbl Name shows the object that was explicitly fragmented.
If you use Dynamic Server, the display includes a Type column to indicate whether the fragment on the line is part of an index or the table data. In Figure 106, the cuts table was created with round-robin strategy, but the index was created without specifying a strategy. In this case, the indexes are located in default dbspaces.
Suppose, when creating an index, you use the following statement to apply a fragmentation strategy:
create index idx on cust(custnum) fragment by expression custnum < 200 in dbspace1, custnum > 200 in dbspace2, remainder in rootdbs;
In this case, the fragmentation display looks like Figure 107.
Idx/Tbl Name Dbspace Type Expression cust dbspace1 T cust dbspace2 T cust rootdbs T idx dbspace1 I (custnum < 200) idx dbspace2 I (custnum > 200) idx rootdbs I remainder
Idx/Tbl Name shows the index name because the fragmentation was explicitly applied to the index.
Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]