Use this wizard to rebuild a table, including dropping and renaming columns.
Notes:
To rebuild a table
Right-click the table in the left-hand side and select Rebuild | Table.
Tip: You can also select Database | Optimize | Rebuild Table.
Select Data, Table Parameters, and Index Parameters as needed to specify any new settings for the table, then click Next.
Note: The parameters in this window are defined by Oracle. See Oracle's documentation for more information.
View the ALTER statement. On this page you can:
Note: If the table was checked out from Team Coding, it is automatically updated after the rebuild is run.
This procedure explains how to rebuild a single index.
Note: You can rebuild multiple indexes and tables at the same time. Rebuild Multiple Objects
To rebuild an index
Select parameters as necessary.
Note: The parameters in this window are defined by Oracle. See Oracle's documentation for more information.
The Rebuild Multiple Objects feature allows you to simultaneously rebuild multiple indexes, tables, or LOB segments.
To rebuild multiple objects
Select the Indexes tab and click .
Tip: You can click to automatically rebuild the recommended indexes, or click
to generate a rebuild script for the recommended indexes (the script is copied to the clipboard and you can paste it into the Editor).
Tab/Option | Description |
---|---|
Thresholds and Performance Options tab | Use the following option to... |
Use 'Online' option |
Have Toad rebuild or move the table or index while it is in use. |
Storage Clause Adjustments - Extents tab |
Use the following option to... |
Change Extent Sizes to the Following |
Change the extent sizes, which overrides any options set in the top part of the window. If you opt to use this feature, make sure you examine the index before you use it. Because the percent used is a factor, this value can only be obtained by examining the indexes. Note that this is not the PCTUSED storage parameter. This refers to the actual percentage of allocated storage space for the index being used. |
Adjust Extent Sizes to Minimize # of Extents |
Minimize the number of extents. When this option is selected, the new extent size for each index is calculated as follows: working size equals the total size multiplied by the percent used. This working size is then passed through the Make extent this size or Round All Extent Sizes to the Nearest Power of... algorithm, as selected. The resulting value is the new initial_extent size. It is also the new next_extent size. Pctincrease is set to zero. Caution: If some indexed tables are used as large temporary tables but are usually empty, Toad may recommend that you rebuild them because they have zero percent used. If you use Adjust Extent Sizes during the rebuild, Toad would build the index with small extents that may not hold all of your data later. Avoid this by either using global temporary tables, or do not rebuild indexes with a percent used of zero. |
Storage Clause Adjustments - Tablespaces Tab |
Select options to move all objects to different tablespaces, or selectively dependent upon their size.
|
Email Notifications tab |
Select whether to send email notifications after completion. The email is sent to the recipients defined on the Email Settings options page. See "Email Settings" in the online help for more information. |
Toad provides an intuitive and efficient way to write, run, and test your SQL and PL/SQL code. Toad supports efficient code management for a single developer or a whole team of developers.
© ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center