ER/Studio - Embarcadero Technologies Product Documentation
ER/Studio - Embarcadero Technologies Product Documentation ER/Studio - Embarcadero Technologies Product Documentation
USING ER/STUDIO > DEVELOPING THE PHYSICAL MODEL • No Sort: (NOSORT) If selected, specifies to not sort the data when the index is rebuilt. • Reverse Byte Order: If selected, reverses the bytes of each column indexed (except the rowid) while keeping the column order. By reversing the keys of the index, the insertions will be distributed across all leaf keys in the index. • Enable Compression: (COMPRESS) Select to enable index compression. Compression can repress duplication of keys in non-unique indexes. For concatenated indexes (indexes with multiple columns), the compress option can reduce the size of the index by more than half. For concatenated indexes (indexes with multiple columns), compression can reduce the size of the index by more than half. The compress option allows you to specify the prefix length for multiple column indexes. • Prefix Length: This is the prefix length for multiple column indexes. • Tablespace: Displays the tablespace on which the table index is stored. • No Logging: Select, if you do not want the DLL operations to be logged in the redo file. This can reduce index creation and updates by up to 30%. • Pct Free: (PCTFREE) Specifies the maximum percentage of space in each data block to reserve for future updates. This reserved space helps to avoid row migration and chaining caused by an update operation that extends a data row's length. Tables that won’t be updated should have this value set to 0. • Initial Trans: (INITTRANS) Specifies the number of DML transactions for which space is initially reserved in the data block header. Oracle stores control information in the data block to indicate which rows in the block contain committed and uncommitted changes. The amount of history that is retained is controlled by this parameter. If too many transactions concurrently modify the same data block in a very short period, Oracle may not have sufficient history information to determine whether a row has been updated by a too recent transaction. Initial Transactions limit the minimum number of concurrent transactions that can update a data block to avoid the overhead of allocating a transaction entry dynamically. Specify a higher value for indexes that may experience many transactions updating the same blocks. • Max Trans: (MAXTRANS) Specifies the maximum number of concurrent transactions that can update a data block to avoid performance problems. Once the space reserved by INITRANS is depleted, space for additional transaction entries is allocated out of any available free space. Once allocated, this space effectively becomes a permanent part of the block header. This parameter limits the number of transaction entries that can concurrently use data in a data block and therefore limits the amount of free space that can be allocated for transaction entries in a data block. • Parallel: Selects Oracle's parallel query option. You can achieve substantial performance gains by using Oracle's parallel query option. • Degrees: Specifies the number of query server processes that should be used in the operation. • Instances: Specifies how you want the parallel query partitioned between the parallel servers. • Initial Extent: (INITEXTENT) Specifies the initial number of data blocks that Oracle should reserve. Oracle will reserve the number of data blocks that correspond to the initial extent for that table’s rows. • Next Extent: (NEXT) Specifies the size in kilobytes of the next extent. You should monitor this figure against the largest available chunk of free space in the tablespace. If a table cannot allocate its next extent, it will no longer be able to extend and, therefore, cannot accept additional data. • Pct Increase: (PCTINCREASE) Specifies the percentage by which the next extent should grow over the previous extent's size. Be careful when setting Percent Increase because it magnifies how an object grows and, therefore, can materially affect available free space in a tablespace. • Min Extents: (MINEXTENTS) Specifies the number of extents to allocate when the segment is created. Controls free space fragmentation by making sure that every used or free extent is at least as large as the value you specify. • Max Extents: (MAXEXTENTS) Specifies the maximum number of extents that Oracle can allocate to the index. Once this limit is reached, Oracle prevents further growth of the cluster and cannot accept additional data. Carefully monitor the number extents already allocated to the index with this limit. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 168
USING ER/STUDIO > DEVELOPING THE PHYSICAL MODEL • Free Lists: (FREELISTS) Specifies the number of free lists to apply to the table. The default and minimum value is 1. Free lists can help manage the allocation of data blocks when concurrent processes are issued against the index. Oracle uses the free list to determine which data block to use when an INSERT operation occurs. Oracle allows table and indexes to be defined with multiple free lists. All tables and index free lists should be set to the high-water mark of concurrent INSERT or UPDATE activity. For example, if the index has up to 20 end users performing INSERTs at any time, then the index should have FREELISTS=20.Too low a value for free lists will cause poor Oracle performance. An increase in FREELISTS or FREELIST GROUPS can alleviate segment header contention. • Free List Groups: (FREELIST GROUPS) Applicable only if you are using Oracle with the Parallel Server option in parallel mode. Specifies the number of free list groups which allow the table to have several segment headers. This enables multiple tasks to insert into the index; thereby alleviating segment header contention. Free list groups should be set to the number of Oracle Parallel Server instances that access the index. For partitioned objects and cases of segment header contention, free list groups my be set for non-RAC systems. • Buffer Pools: (BUFFER_POOL) Specifies the memory structure or buffer pool that is used for caching data blocks in memory, providing faster data access. • DEFAULT: Caches data blocks in the default buffer pool. • KEEP: Retains the object in memory to avoid I/O conflicts. • RECYCLE: Moves data blocks from memory as soon as they are no longer in use, thereby saving cache space. Options tab Options available depend on the database platform selected. For information on the index options available for your database platform, click a link below: • Hitachi HiRDB Index Options • IBM DB2 for AS/400, Common Server, and UDB Versions 5 through 9 Index Options • IBM DB2 for OS/390 Index Options • Informix Index Options • Interbase Index Options • Microsoft Access and SQL Server Index Options • MySQL Index Options • NCR Teradata Index Options • Oracle 7 Index Options • Postgre SQL Index Options • Sybase Index Options Hitachi HiRDB Index Options • Unique: (UNIQUE) If selected, specifies that the index key contains no duplicate values and therefore every row in the table is in some way unique. If not selected, a non-unique index is created that lets table rows have duplicate values in the columns that define the index. IBM DB2 for AS/400, Common Server, and UDB Versions 5 through 9 Index Options • Unique: (UNIQUE) If selected, specifies that the index key contains no duplicate values and therefore every row in the table is in some way unique. If not selected, a non-unique index is created that lets table rows have duplicate values in the columns that define the index. EMBARCADERO TECHNOLOGIES > ER/STUDIO® 8.0.3 USER GUIDE 169
- Page 117 and 118: USING ER/STUDIO > DEVELOPING THE LO
- Page 119 and 120: USING ER/STUDIO > DEVELOPING THE LO
- Page 121 and 122: USING ER/STUDIO > DEVELOPING THE LO
- Page 123 and 124: USING ER/STUDIO > DEVELOPING THE LO
- Page 125 and 126: USING ER/STUDIO > DEVELOPING THE LO
- Page 127 and 128: USING ER/STUDIO > DEVELOPING THE LO
- Page 129 and 130: USING ER/STUDIO > DEVELOPING THE LO
- Page 131 and 132: USING ER/STUDIO > DEVELOPING THE LO
- Page 133 and 134: USING ER/STUDIO > DEVELOPING THE LO
- Page 135 and 136: USING ER/STUDIO > DEVELOPING THE LO
- Page 137 and 138: USING ER/STUDIO > DEVELOPING THE LO
- Page 139 and 140: USING ER/STUDIO > DEVELOPING THE LO
- Page 141 and 142: USING ER/STUDIO > DEVELOPING THE LO
- Page 143 and 144: USING ER/STUDIO > DEVELOPING THE PH
- Page 145 and 146: USING ER/STUDIO > DEVELOPING THE PH
- Page 147 and 148: USING ER/STUDIO > DEVELOPING THE PH
- Page 149 and 150: USING ER/STUDIO > DEVELOPING THE PH
- Page 151 and 152: USING ER/STUDIO > DEVELOPING THE PH
- Page 153 and 154: USING ER/STUDIO > DEVELOPING THE PH
- Page 155 and 156: USING ER/STUDIO > DEVELOPING THE PH
- Page 157 and 158: USING ER/STUDIO > DEVELOPING THE PH
- Page 159 and 160: USING ER/STUDIO > DEVELOPING THE PH
- Page 161 and 162: USING ER/STUDIO > DEVELOPING THE PH
- Page 163 and 164: USING ER/STUDIO > DEVELOPING THE PH
- Page 165 and 166: USING ER/STUDIO > DEVELOPING THE PH
- Page 167: USING ER/STUDIO > DEVELOPING THE PH
- Page 171 and 172: USING ER/STUDIO > DEVELOPING THE PH
- Page 173 and 174: USING ER/STUDIO > DEVELOPING THE PH
- Page 175 and 176: USING ER/STUDIO > DEVELOPING THE PH
- Page 177 and 178: USING ER/STUDIO > DEVELOPING THE PH
- Page 179 and 180: USING ER/STUDIO > DEVELOPING THE PH
- Page 181 and 182: USING ER/STUDIO > DEVELOPING THE PH
- Page 183 and 184: USING ER/STUDIO > DEVELOPING THE PH
- Page 185 and 186: USING ER/STUDIO > DEVELOPING THE PH
- Page 187 and 188: USING ER/STUDIO > DEVELOPING THE PH
- Page 189 and 190: USING ER/STUDIO > DEVELOPING THE PH
- Page 191 and 192: USING ER/STUDIO > DEVELOPING THE PH
- Page 193 and 194: USING ER/STUDIO > DEVELOPING THE PH
- Page 195 and 196: USING ER/STUDIO > DEVELOPING THE PH
- Page 197 and 198: USING ER/STUDIO > DEVELOPING THE PH
- Page 199 and 200: USING ER/STUDIO > DEVELOPING THE PH
- Page 201 and 202: USING ER/STUDIO > DEVELOPING THE PH
- Page 203 and 204: USING ER/STUDIO > DEVELOPING THE PH
- Page 205 and 206: USING ER/STUDIO > DEVELOPING THE PH
- Page 207 and 208: USING ER/STUDIO > DEVELOPING THE PH
- Page 209 and 210: USING ER/STUDIO > DEVELOPING THE PH
- Page 211 and 212: USING ER/STUDIO > DEVELOPING THE PH
- Page 213 and 214: USING ER/STUDIO > DEVELOPING THE PH
- Page 215 and 216: USING ER/STUDIO > DEVELOPING THE PH
- Page 217 and 218: USING ER/STUDIO > DEVELOPING THE PH
USING <strong>ER</strong>/STUDIO > DEVELOPING THE PHYSICAL MODEL<br />
• No Sort: (NOSORT) If selected, specifies to not sort the data when the index is rebuilt.<br />
• Reverse Byte Order: If selected, reverses the bytes of each column indexed (except the rowid) while keeping<br />
the column order. By reversing the keys of the index, the insertions will be distributed across all leaf keys in the<br />
index.<br />
• Enable Compression: (COMPRESS) Select to enable index compression. Compression can repress duplication<br />
of keys in non-unique indexes. For concatenated indexes (indexes with multiple columns), the compress option<br />
can reduce the size of the index by more than half. For concatenated indexes (indexes with multiple columns),<br />
compression can reduce the size of the index by more than half. The compress option allows you to specify the<br />
prefix length for multiple column indexes.<br />
• Prefix Length: This is the prefix length for multiple column indexes.<br />
• Tablespace: Displays the tablespace on which the table index is stored.<br />
• No Logging: Select, if you do not want the DLL operations to be logged in the redo file. This can reduce index<br />
creation and updates by up to 30%.<br />
• Pct Free: (PCTFREE) Specifies the maximum percentage of space in each data block to reserve for future<br />
updates. This reserved space helps to avoid row migration and chaining caused by an update operation that<br />
extends a data row's length. Tables that won’t be updated should have this value set to 0.<br />
• Initial Trans: (INITTRANS) Specifies the number of DML transactions for which space is initially reserved in the<br />
data block header. Oracle stores control information in the data block to indicate which rows in the block contain<br />
committed and uncommitted changes. The amount of history that is retained is controlled by this parameter. If too<br />
many transactions concurrently modify the same data block in a very short period, Oracle may not have sufficient<br />
history information to determine whether a row has been updated by a too recent transaction. Initial Transactions<br />
limit the minimum number of concurrent transactions that can update a data block to avoid the overhead of<br />
allocating a transaction entry dynamically. Specify a higher value for indexes that may experience many<br />
transactions updating the same blocks.<br />
• Max Trans: (MAXTRANS) Specifies the maximum number of concurrent transactions that can update a data block<br />
to avoid performance problems. Once the space reserved by INITRANS is depleted, space for additional<br />
transaction entries is allocated out of any available free space. Once allocated, this space effectively becomes a<br />
permanent part of the block header. This parameter limits the number of transaction entries that can concurrently<br />
use data in a data block and therefore limits the amount of free space that can be allocated for transaction entries<br />
in a data block.<br />
• Parallel: Selects Oracle's parallel query option. You can achieve substantial performance gains by using Oracle's<br />
parallel query option.<br />
• Degrees: Specifies the number of query server processes that should be used in the operation.<br />
• Instances: Specifies how you want the parallel query partitioned between the parallel servers.<br />
• Initial Extent: (INITEXTENT) Specifies the initial number of data blocks that Oracle should reserve. Oracle will<br />
reserve the number of data blocks that correspond to the initial extent for that table’s rows.<br />
• Next Extent: (NEXT) Specifies the size in kilobytes of the next extent. You should monitor this figure against the<br />
largest available chunk of free space in the tablespace. If a table cannot allocate its next extent, it will no longer<br />
be able to extend and, therefore, cannot accept additional data.<br />
• Pct Increase: (PCTINCREASE) Specifies the percentage by which the next extent should grow over the previous<br />
extent's size. Be careful when setting Percent Increase because it magnifies how an object grows and, therefore,<br />
can materially affect available free space in a tablespace.<br />
• Min Extents: (MINEXTENTS) Specifies the number of extents to allocate when the segment is created. Controls<br />
free space fragmentation by making sure that every used or free extent is at least as large as the value you<br />
specify.<br />
• Max Extents: (MAXEXTENTS) Specifies the maximum number of extents that Oracle can allocate to the index.<br />
Once this limit is reached, Oracle prevents further growth of the cluster and cannot accept additional data.<br />
Carefully monitor the number extents already allocated to the index with this limit.<br />
EMBARCAD<strong>ER</strong>O TECHNOLOGIES > <strong>ER</strong>/STUDIO® 8.0.3 US<strong>ER</strong> GUIDE 168