Answer:

Alert emails have been enhanced to include information about recent Monitor samples. This extra information may tell you what you need to know without having to open the full Foxhound display.

The Foxhound upgrade process moves the old foxhound.db and log files to a backup folder before they are replaced. For more information see How do I restore the old build of Foxhound after installing a new build?

The Global Database Id value is displayed on the Monitor and Display Schema pages, as well as in Alert emails, if it is set to a non-default value in the target database. This makes it easier to tell different remote databases apart in a replicating or synchronizing environment.

The maximum number of active connections displayed on the Monitor page has been reduced from 100 to 10 because a long dynamically-refreshed list is not very usable. You may use the manually-refreshed History page to see more connections.

The "Last Statement" column has been moved to a separate line in the Connections section of the Monitor and History pages. This makes the Connections display more readable by reducing the amount of left-right scrolling required. It also makes it less likely the Last Statement will be wrapped.

The Monitor and History displays now show dashes "-" for all omitted column values instead of empty spaces. This makes it clear which values are not available or not applicable, and it also makes the resulting text somewhat easier to read when you use copy-and-paste. For example, the "CPU Time" percentage appears as a dash "-" for the first sample because it can only be calculated for second and later samples.

Note: This use of dashes "-" does not apply to columns which have been entirely omitted because the data is not available for the version of SQL Anywhere being used for the target database; e.g., the "CPU Time" column does not appear at all for version 5 and 6 target databases.

• you won't lose any data when Foxhound goes GA (Generally Available) and you install a new build of Foxhound and activate it with Full functionality,

• you won't lose any data when you try out future Beta builds after activating Foxhound with Full functionality.

• you may have to obtain a new (free) registration key to switch back to Full functionality after testing a Beta build.

The following bug has been fixed: When sampling was started after it was stopped by the "safe startup" process, the first sample was sometimes incorrectly shown as occurring between the "-- Sampling stopped by Safe Startup at --" and "-- Sampling stopped by Safe Startup --" entries:

5:42:55 AM  7m 17.4s  -- Sampling stopped by Safe Startup --  
5:42:06 AM  0s        0s / 0s    1    1 / - / -  1 / 100 / - ...
5:35:38 AM  .5s       -- Sampling stopped by Safe Startup at --  

The following bug has been fixed: Alert #20 was issued for every target database running on SQL Anywhere version 5.5 even though the information required to calculate cache satisfaction is not available for that version. A value of zero is no longer assumed and the following Alert is no longer issued for target databases running on version 5.5:

Alert #20: The cache satisfaction (hits/reads) has fallen to 90% or lower for 10 or more recent samples.

The following bug has been fixed: When Foxhound was stopped and restarted, a successful sample was sometimes incorrectly shown as occurring between the "-- Foxhound stopped at --" and "-- Foxhound stopped --" entries:

8:23:36 AM  10.4s      0s / .3s ...
8:23:26 AM  59.2s      -- Sampling stopped by Safe Startup -- 
8:22:27 AM  1.6s       -- Sampling stopped by Safe Startup at -- 
8:22:25 AM  14m 25.7s  -- Foxhound stopped -- 
8:08:01 AM  10.6s      0s / .1s ...
8:07:59 AM  -          -- Foxhound stopped at -- 
8:07:50 AM  10.0s      0s / 0s ...

The Alerts Criteria page has been fixed so the Restore Factory Settings button no longer wipes out the values you've put in the following fields:

• Send Alert Emails

• Email address(es)

• Use HTML, Host[:port]

The "Frequently Asked Questions" section of the Foxhound website has been updated:

How do I backup my Foxhound database?
How do I backup my Foxhound database on a regular basis?
How do I change the Alerts criteria? (threshold settings, etcetera)
How do I get something to show up in the Last Statement column?
How do I get something to show up in the Total Waits, Waiting Time columns?
How do I install version 11 of SQL Anywhere on the same machine used to run an earlier version of SQL Anywhere?
How do I keep the Foxhound database file from growing so large?
How do I reinstall an earlier build of Foxhound?
How do I restore the Foxhound database from a backup?
How do I restore the old build of Foxhound after installing a new build?
How do I tell different databases apart in Alert emails?

What is the upgrade policy for installing new builds of Foxhound?

Why are my Alert emails garbled?
Why are the values empty in the Last Statement column?
Why are the values empty in the Total Waits, Waiting Time columns?
Why are the values so large in the Interval and Sample Time columns?
Why does the CPU Time for a blocked connection go up over time?
Why does the Foxhound post upgrade process take so long?
Why doesn't the Foxhound backup process create the generation2 subfolder?
Why is the "Choose a DSN:" drop down list empty?

Messages...
404 Not Found
503 Service Temporarily Unavailable
A subdirectory or file backup already exists.
ALERT #xx - xxx - xxx(nn)
Alert #11 - HA failover - ... on ...
ALL CLEAR #xx - xxx - xxx(nn)
CANCELLED #xx - xxx - xxx(nn)
Connection timeout for target ... after ... (timeout threshold is ...; see Foxhound Options)
Data cannot be upgraded from ... to ...
EMAIL FAILURE - SMTP send email failed with return code ... when sending "..."
Specified database file already in use
The system cannot find the file specified.
User "DBA" dropped event connection 1000...... ("rroad_monitor_sample_loop")

See also...
What is Foxhound?
How do I get a copy of Foxhound?