Answer:

The most effective way to make the upgrade process faster is to change the FOXHOUND1UPGRADE value from ALL to some other value during the post-update stage of the Foxhound installation process:

******************************************************************
*** You can control how much of the existing data is upgraded.
*** To do that, you can set the FOXHOUND1UPGRADE environment
***   variable BEFORE running this upgrade process,
***   OR you can type in a temporary override here.
***
*** The current setting is...
***   FOXHOUND1UPGRADE=ALL which means upgrade all the data
***
*** If you want to CHANGE the setting, type in a new value...
***       ALL       - upgrade all the data
***       OPTIONS   - no samples, just the Foxhound options
***       yyyymmdd  - options plus samples since yyyymmdd
***       nnn       - options plus last nnn days of samples
***       NOTHING   - don't upgrade any data
*** ...and press Enter to continue.
*** You will be asked to "CONFIRM OR CHANGE" again.
***
*** If you LIKE the current setting, just press Enter.
******************************************************************
Current FOXHOUND1UPGRADE=ALL
New     FOXHOUND1UPGRADE=

Note: In all cases, Foxhound will preserve the existing copy of the Foxhound database and transaction log files in the backup\previous_build folder. See How do I restore the old build of Foxhound after installing a new build?

Here's how the different FOXHOUND1UPGRADE values work; the following descriptions apply even if you are "upgrading" to exactly the same version of Foxhound; i.e., you are reinstalling the same version in order to shrink and/or reorganize the Foxhound database.

• ALL    Upgrade all the data.

  If sampling was enabled before the upgrade process was started, sampling will start again as soon as you start Foxhound after the upgrade is finished.

  In this case only, Foxhound will use the ALTER DBSPACE SYSTEM ADD command to expand the new Foxhound database file to accomodate all the data plus 10% before starting to copy the data. The new Foxhound database file won't be much (or any) smaller than the old one, but it will be reorganized by the upgrade process.

• OPTIONS    Upgrade all the Foxhound settings and options, including the Foxhound activation status and the Monitor Options for all the target databases, but don't copy any of the sample data.

  If sampling was enabled before the upgrade process was started, sampling will start again as soon as you start Foxhound after the upgrade is finished.

  In this case, Foxhound will not use ALTER DBSPACE SYSTEM ADD to expand the new database file, with the result being the new Foxhound database file will be quite small.

• yyyymmdd    Upgrade all the Foxhound options plus all the samples recorded since yyyymmdd. You can specify any valid timestamp as long as it at least 8 characters long and in the past, but no more than 100000 days in the past; e.g., 20110801, 2011-08-01 23:59:59.999, 2011-7-7 12 are all valid timestamps.

  Caution: If you specify a timestamp more than 100000 days in the past, Foxhound will use the OPTIONS setting and no samples at all will be copied.

  Foxhound chooses OPTIONS because it runs quickly so you don't have to wait so long if it was a mistake. To correct the error, restore the old copy of the Foxhound database and reinstall Foxhound again. See How do I restore the old build of Foxhound after installing a new build?

  If sampling was enabled before the upgrade process was started, sampling will start again as soon as you start Foxhound after the upgrade is finished.

  In this case, Foxhound will not use ALTER DBSPACE SYSTEM ADD to expand the new database file even if yyyymmdd is earlier than the earliest recorded sample. In other words, you can use an old yyyymmdd to copy all the data while at the same time reorganizing and shrinking the Foxhound database.

• nnn    Upgrade all the Foxhound options plus all the samples recorded in the past nnn days. You can specify any positive integer from 1 to 100000.

  Caution: If you specify a number outside the range 1 to 100000, Foxhound will use the OPTIONS setting and no samples at all will be copied.

  Foxhound chooses OPTIONS because it runs quickly so you don't have to wait so long if it was a mistake. To correct the error, restore the old copy of the Foxhound database and reinstall Foxhound again. See How do I restore the old build of Foxhound after installing a new build?

  Here is the formula used to convert nnn into a timestamp: DATEADD ( DAY, -nnn, CURRENT TIMESTAMP )

  If sampling was enabled before the upgrade process was started, sampling will start again as soon as you start Foxhound after the upgrade is finished.

  In this case, Foxhound will not use ALTER DBSPACE SYSTEM ADD to expand the new database file even if nnn is earlier than the earliest recorded sample. In other words, you can use a large nnn to copy all the data while at the same time reorganizing and shrinking the Foxhound database.

• NOTHING    Don't upgrade any data, no options or settings, not even the activation status.

  Note: Even in this case, Foxhound will preserve the existing copy of the Foxhound database and transaction log files in the backup\previous_build folder. See How do I restore the old build of Foxhound after installing a new build?

• EVERYTHING    Same as ALL.

• SETTINGS    Same as OPTIONS.

• NONE    Same as NOTHING.

• FRESH    Same as NOTHING.

See also...
How do I install Foxhound?
How do I reinstall Foxhound?
How do I upgrade Foxhound from one edition to another?
How do I restore the old build of Foxhound after installing a new build?