Question: What are the differences among the different editions of Foxhound: Rental, Basic and Extended?
Answer: The following chart is subject to change.
General Characteristics
|
| Rental | Basic | Extended |
| | | |
Type of registration key
required for activation
|
Rental |
Basic |
Extended |
How you obtain a
registration key
|
Purchase online |
Purchase online |
Purchase online |
Installed copy
will expire
|
Yes, when the
rental period
expires
|
No |
No |
Installed copy may be renewed before
or after expiry date
|
Yes, via purchase of
another Rental
registration key
|
- |
- |
How is the new expiry
date for a renewal
calculated?
|
By adding a new rental
period to the current
date or existing expiry
date, whichever is later
|
- |
- |
Activation upgrade to a
different edition
is available
|
Yes, via purchase of a
New Basic Key or a
New Extended Key
|
Yes, via purchase of a
Basic To Extended Key
|
- |
Adhoc reporting is
always available
|
Yes, even after
the rental period
expires
|
Yes
|
Yes
|
Limitations on the Database Monitor
|
| Rental | Basic | Extended |
| | | |
Schedules may be used
to control when samples
are recorded
|
No |
No |
Yes |
Schedules may be used
to control when Alert
emails are sent
|
No |
No |
Yes |
The AutoDrop feature may
be used to automatically
drop errant connections
|
No |
No |
Yes |
Maximum number of
connections to each
target database
|
100 * |
100 * |
No limit |
Maximum number of physical
CPUs used for each target
database on a SQL Anywhere
Version 10, 11, 12, 16 server
|
1 ** |
1 ** |
No limit |
Target database may run on a
SQL Anywhere 11.0.1 or later
Standard or Advanced Edition
server
|
No *** |
No *** |
Yes |
Maximum number of target
databases which may be
monitored at the same time
by a single copy of Foxhound
|
10 |
10 |
100 |
Maximum number of different
server names which may be
used when starting separate
instances of Foxhound ****
|
1 **** |
1 **** |
Unlimited **** |
| | | |
|
* This limit on connections applies to all versions and editions of SQL Anywhere target databases and servers.
The actual limit is 101 connections when you count the connection from Foxhound itself. Internal connections
(e.g., connections made by events and web services) are counted in the total.
** This limit on physical CPUs does not apply to SQL Anywhere version 5.5, 6, 7, 8 or 9 target databases and servers.
Also, it applies to the number of physical processors as given by the NumPhysicalProcessorsUsed server property,
not the number of logical processors shown by "Using n CPUs" value in the Foxhound Database Monitor.
For example, a single Intel Pentium 4 processor counts as 1 physical processor even
though the separate HyperThreading units may show up as "Using 2 CPUs". Similarly, a single Intel Core2 Quad
processor also counts as only 1 physical processor even though it may show up as "Using 4 CPUs".
*** This restriction on SQL Anywhere editions does not apply to SQL Anywhere target databases and servers earlier than version 11.0.1,
which is when SQL Anywhere introduced the notion of different editions.
**** The Rental and Basic Editions allow only one instance of Foxhound
to be started on the same local network, and the SQL Anywhere server name must be "foxhound3".
The Extended Edition allows an unlimited number of Foxhound instances to be started on the same local network,
with no restrictions on the SQL Anywhere server names; however, the License Agreement requires that a
separate Extended Edition registration key be purchased for each multiple of 10 instances started.
See also...
How do I get a copy of Foxhound?
What happens when a copy of Foxhound expires?
What is the upgrade policy for installing new builds of Foxhound?
What is the Foxhound End-User License Agreement (EULA)?
Foxhound Extended edition is required for ...
What are the Foxhound system requirements?
How many target databases can one copy of Foxhound monitor?
Help - Introduction - Starting Multiple Copies of Foxhound
|