Displays the system, instance, and name of the currently selected database.
Displays the node number and name of the currently selected database partition.
Calculates new parameters.
Go through all the pages of the wizard to recalculate new suggested configuration parameters.
Use this option if the amount of data in your database has increased or decreased, your server has more memory, or you want to change any of your selections on one of the pages of the wizard.
Restores the parameters saved on the date and time shown.
Go through just the first page (Introduction) and the last page (Results) of the wizard to restore the saved configuration parameters.
Use this option if the last set of configuration parameters suggested by the Configure Performance wizard did not adequately improve your performance. The configuration parameters that were in effect before you applied the suggested parameters will be reapplied to your database.
Move the slider bar to select the amount of memory that you want to devote to database processing. The physical memory shows the amount of installed RAM detected on the server.
Categorizes your database usage. The database will be optimized for queries.
The Transactions page is hidden.
Categorizes your database usage. The database parameters will be set to balance the performance of queries and transactions.
The Transactions page is visible.
Categorizes your database usage. The database will be optimized for transactions.
The Transactions page is visible.
Each transaction has 10 or more SQL statements in a single unit of work.
Note that long transactions tend to consume more resources for a longer period of time than do short transactions.
Each transaction has 1 - 9 SQL statements in a single unit of work.
Estimate the number of transactions per minute for your database.
Type a number in the range 1 - 10 000, or use the spin buttons to increase or decrease the displayed value.
You can use performance monitoring to get a better estimate for this value. The default value is 60.
Database parameters will be set for faster transactions and longer roll-forward time during recovery. The default is Both.
Database parameters will be set to balance transaction performance with time to recover. This is the default.
Database parameters will be set for faster recovery and slightly slower transaction performance. The default is Both.
Select this option if there is any data in the database.
The new size of the database will be used to calculate a new set of recommended configuration parameters. The default is Yes.
Select this option if this is a new database with empty tables.
The new size of the database will be used to calculate a new set of recommended configuration parameters. The default is Yes.
Type the average number of local applications connected to the database at any one time. Local applications run on the same machine as this database.
Use the spin buttons to increase or decrease the displayed value. The default is 0.
Type the average number of remote applications connected to the database at any one time. Remote applications run on a different machine from this database.
Use the spin buttons to increase or decrease the displayed value. The default is 10.
Locks all rows that an application references within a unit of work. Using repeatable read, a SELECT statement issued by an application twice within the same unit of work in which the cursor was opened, gives the same result each time. With repeatable read, lost updates, access to uncommitted data, and phantom rows are not possible.
The repeatable read isolation level ensures that all returned data remains unchanged until the time the application sees the data, even when temporary tables or row blocking are used. This is the default.
For more information, see the Concurrency section in the Administration Guide.
Locks only those rows that an application retrieves within a unit of work. It ensures that any qualifying row read during a unit of work is not changed by other application processes until the unit of work completes, and that any row changed by another application process is not read until the change is committed by that process. That is, "nonrepeatable read" behavior is not possible.
The read stability isolation level ensures that all returned data remains unchanged until the time the application sees the data, even when temporary tables or row blocking are used.
For more information, see the Concurrency section in the Administration Guide.
Locks any row accessed by a transaction of an application while the cursor is positioned on the row. This lock remains in effect until the next row is fetched or the transaction is terminated. However, if any data on a row is changed, the lock must be held until the change is committed to the database.
With cursor stability, both nonrepeatable read and the phantom read phenomenon are possible. Cursor stability should be used when you want the maximum concurrency while seeing only committed rows for other applications.
For more information, see the Concurrency section in the Administration Guide.
Allows an application to access uncommitted changes of other transactions. The application also does not lock other applications out of the row it is reading, unless the other application attempts to drop or alter the table. Uncommitted read works differently for read-only and updatable cursors.
The uncommitted read isolation level is most commonly used for queries on read-only tables, or if you are only executing select-statements and you do not care whether you see uncommitted data from other applications.
For more information, see the Concurrency section in the Administration Guide.
Lists configuration parameters, their current values, the recommended values, and the DB2 parameters.
Select this check box if you want to apply the recommended values to the current database as soon as you click Finish.
If you select this check box and click Finish, the changes will not take effect until the next db2start command is issued.
You can click Finish only after you have selected at least one of the check boxes on this page.
Select this check box if you want to save a script file that can apply the recommended values to the current database. Use the Script Center to run or schedule the script. This is the default.
After you have run the script and you are ready for the new configuration parameters to take effect, stop the instance and then restart the instance.
Rebind your packages, if necessary.
The file is saved when you click Finish.
You can click Finish only after you have selected at least one of the check boxes on this page.
Specifies the drive, path, and name of a file. You can either type the fully qualified name, or open the Browse File window by clicking the [...] push button.
This field is available only when Save to Script Center is selected.
Type a description of the script in this entry field.
This field is available only when Save to Script Center is selected.
The description will appear with the script in the Script Center.