The About Foxhound Page

The About Foxhound page displays version and other information about this copy of Foxhound.

The Foxhound Version shows the major version of this copy of Foxhound.

The ... built at ... line identifies the exact build number of this copy of Foxhound, as well as the timestamps for the Foxhound build and database creation.

The Serial Number: may be useful when requesting support.

The button will appear for a Rental Edition copy of Foxhound so you can renew the rental period or upgrade to the Basic or Extended Edition.

The button will appear for a Basic Edition copy of Foxhound so you can upgrade it to the Extended Edition.

The "Original Full Build Number" may be necessary when applying future upgrades.

The Foxhound database folder (DBFOLDER): is where the currently running copy of the Foxhound database file plus other associated files and subfolders are located. This folder may be where Foxhound was installed, but it will be different when multiple copies of the Foxhound database are created. DBFOLDER is the name of a local environment variable used by several Foxhound command files.

For more information see Starting Multiple Copies of Foxhound.

The Foxhound server name (SERVER): is the dbsrv17 -n option used for the currently running copy of the Foxhound engine. This name may be foxhound5 for the original installed copy of Foxhound, but it will be different when multiple instances of the Foxhound engine are started. SERVER is the name of a local environment variable used by several Foxhound command files.

For more information see Starting Multiple Copies of Foxhound.

The Foxhound command line: lists all the SQL Anywhere 16 options used to start the Foxhound database.

The Foxhound Windows API support DLL: line shows

rroad5_sa17_bin32.dll if Foxhound is running on the 32-bit version of SQL Anywhere 17.
rroad5_sa17_bin64.dll if Foxhound is running on the 64-bit version of SQL Anywhere 17.

For more information see the FOXHOUND5BIN Optional Environment Variable.

The Foxhound is running on @@VERSION:line shows the exact version and build of SQL Anywhere that's currently running the Foxhound database.

The Foxhound is running in safe mode:line displays Y or N.

For more information see Safe Mode Startup.

The Foxhound Process ID: line displays the Windows Process Identifier for the instance of SQL Anywhere that is running Foxhound. This number can be displayed in the Windows Task Manager window, and it can be used in the Windows TASKKILL command; e.g., taskkill /pid 3644

For more information see Monitor Options - Monitor Connection Name.

The File created by most recent Mini-Backup: line shows the file specification of the most recent Mini-Backup file that has been created.

For more information see Foxhound Options - Mini-Backup.

The File used by most recent Mini-Restore: line shows which (if any) Mini-Backup file was used to load this copy of Foxhound with options and settings but no sample data.

For more information see Foxhound Options - Mini-Restore.

The Patch File table is displayed if any patches have been processed when Foxhound is started.

The Patch File column contains the unique file names of patches that have been read and stored in the rroad_patch table. Each patch file is read only once, but it may be applied more than once.
The Stored At column is when the file was read and stored in the rroad_patch table.
The Applied OK? column is Y if the patch was successfully applied; otherwise it is N.

Note that when the Mini-Restore process is run, or the Foxhound is re-installed to upgrade the data from an existing copy of the same build, any Applied OK? value of Y will be set to N to force previous patches to be re-applied.

The Applied At column is when the patch was successfully applied. This timestamp will change and the Stored At will remain the same when a patch is re-applied after a Mini-Restore or Data Upgrade with the same build number.
The Status column describes what happened when the patch was processed. Patches with Applied OK = Y will have Status = "Patch applied OK" and may be re-applied after a Mini-Restore or Data Upgrade with the same build number.

Patches with Applied OK = N and a non-empty Status value are failures and will not be re-applied.
Patches with Applied OK = N and an empty Status value have not yet been applied at all, successfully or unsuccessfully... this condition is not expected.

[Top]