Foxhound 1.2 FAQ: What ... ? (general)

Foxhound 1.2 FAQ	Loading
	Foxhound 1.2 FAQ Home Foxhound Home RisingRoad Breck.Carter@gmail.com

What ... ? (general)

What is Foxhound? (and how do I get a copy of Foxhound?)
What is SQL Anywhere?
What are the differences among the different editions of Foxhound: Evaluation, Basic and Extended?
What are the Foxhound system requirements?
What is the Foxhound End-User License Agreement (EULA)?
What is the upgrade policy for installing new builds of Foxhound?
What happens when a copy of Foxhound expires?
What's new in Foxhound 1.2?
What is the history of Foxhound?
What environment variables are used by Foxhound?
What HTTP port should I use for Foxhound?
What happened to Foxhound Options - Export Samples?
What is the foxhound1.db ... .ORIGINAL_COPY file?

[ Top ]

Question: What is Foxhound?

Answer: Foxhound is two products in one: it is both a database monitor and a schema troubleshooter for SQL Anywhere.

A database monitor is a computer program that measures the activity of a database management system and displays those measurements in a meaningful way, so that you can easily see that everything's OK or quickly learn about problems and threats to performance and availability. A monitor can also send email alerts when something goes wrong.

A schema troubleshooter is a computer program that performs a static analysis of the tables, columns, indexes, foreign key relationships and other objects in the database, displays those objects in a way that's easy to understand and easy to navigate, together with various facts, figures and curiosities which may be problems that need attention.

[ Top ]

Question: What is SQL Anywhere?

Answer: "SQL Anywhere is a relational database management system (RDBMS) product from the company Sybase iAnywhere, a subsidiary of Sybase."
- from the Wikipedia page

"SQL Anywhere is a comprehensive suite of solutions that provides data management, synchronization and data exchange technologies that enable the rapid development and deployment of database-powered applications in remote and mobile environments."
- from the Sybase product page

[ Top ]

Question: What are the differences among the different editions of Foxhound: Evaluation, Basic and Extended?

Answer: The following chart is subject to change.

General Characteristics

Evaluation Basic Extended

Type of download file
required for installation GA GA GA

Type of registration key
required for activation Evaluation Basic Extended

How you obtain a
registration key Request via email Purchase online Purchase online

Installed copy
will expire After a fixed number
of days following
activation No No

Activation upgrade to a
different edition
is available Yes, to Basic or
Extended Yes, to Extended -

Free upgrades to new
builds are available Yes Yes, until the Free
Upgrade period ends Yes, until the Free
Upgrade period ends

Upgrade to a new build may
change the expiry date No - -

Retail price Free US$195.00 US$395.00

Limitations on Database Monitor

Evaluation Basic Extended

Maximum number of
connections to each
target database No limit 100 * No limit

Maximum number of physical
CPUs used for each target
database on a SQL Anywhere
Version 10, 11 or 12 server No limit 1 ** No limit

Target database may run on a
SQL Anywhere 11.0.1 Standard
or Advanced Edition server Yes No *** Yes

Maximum number of target
databases which may be
monitored at the same time
by a single copy of Foxhound 100 10 **** 100

Maximum number of different
server names which may be
used when starting separate
instances of Foxhound ***** 10 1 ****** 10

* 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 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.
**** This limit on the number of monitor sessions does not apply to the Foxhound Evaluation edition because that edition may be used to fully test and evaluate Foxhound for a limited time before the Extended edition is installed.
***** For all Foxhound editions except the Basic edition, up to 10 separate copies of the Foxhound database may be created, and these separate copies may be started at the same time using separate SQL Anywhere servers running on the same physical computer or on separate computers on the same local network. The following runtime server names are allowed: foxhound1 (the default) and foxhound1b through foxhound1j.
****** This limit on the number of Foxhound copies does not apply to the Foxhound Evaluation edition because that edition may be used to fully test and evaluate Foxhound for a limited time before the Extended edition is installed.

[ Top ]

Question: What are the Foxhound system requirements?

Answer:

1. Windows - Foxhound works with target databases running on other operating systems but the Foxhound engine itself only runs on Windows, and has been tested on Microsoft Windows 7.

2. ODBC - Foxhound itself uses ODBC to connect to your target databases. You don't necessarily need ODBC installed on the servers running your target databases, and you can specify DSN-less connections for Foxhound by using the "String" tab on the main menu page.

3. Chrome, Firefox, IE - The Foxhound client has been tested with the latest browser versions, currently Google Chrome 12, Firefox 5 and Internet Explorer 9.

4. JavaScript - Foxhound needs "JavaScript" or "Active scripting" to be enabled in your browser.

5. SQL Anywhere version 5.5.5.2787 through version 12 for target databases - If you have any target databases running on SQL Anywhere 5.5, you may have to upgrade them to 5.5.5.2787 for Foxhound to work properly with them.

6. SQL Anywhere 12.0.1.3298 or later for Foxhound - Foxhound works with target databases using 5.5 to 12 of SQL Anywhere but the Foxhound engine itself needs the 32-bit or 64-bit version of SQL Anywhere 12.0.1.3298 or later to run.

7. SQLANY12 - The delivered *.bat files expect that the SQLANY12 environment variable points to SQL Anywhere 12. If that is not the case you may have to modify the *.bat files. Here is the default setting on Windows XP, Vista and Windows 7:

   SET SQLANY12=C:\Program Files\SQL Anywhere 12

8. FOXHOUND1 - The delivered *.bat files expect that the FOXHOUND1 environment variable will be created by the Foxhound installation (which will happen by default). If that is not the case you may have to modify the *.bat files. Here is the default setting for Windows XP:

   SET FOXHOUND1=C:\Documents and Settings\All Users\Application Data\RisingRoad\Foxhound1\

and for Windows Vista and Windows 7 it is this:

   SET FOXHOUND1=C:\ProgramData\RisingRoad\Foxhound\

9. Disk space - When re-installing or upgrading Foxhound, 60% or more extra disk space may be required during the post-setup process. The "60% or more" figure applies to the amount of disk space occupied by the existing Foxhound installation, not the total used disk space on the drive.

[ Top ]

Question: What is the Foxhound End-User License Agreement (EULA)?

Answer: RisingRoad - 3QC Inc. License Terms

Foxhound Version 1

By using the software, you accept the following terms. IF YOU DO NOT ACCEPT THEM, DO NOT USE THE SOFTWARE.

1. No-Nonsense License Agreement

The Foxhound software is protected by United States and Canadian copyright law and international copyright treaty provisions. Therefore, you must treat Foxhound just like a book, except that you may copy it onto a computer to be used and you may make archival copies of Foxhound for the sole purpose of backing-up our software and your data and protecting your investment from loss.

By saying "just like a book," RisingRoad means, for example, that one copy of Foxhound may be executed on any number of computers, and may be freely moved from one computer to another, so long as there is no possibility of it being executed on one computer while it's being executed on another.

By saying "one copy of Foxhound", RisingRoad means a copy of the Foxhound software that has been activated by the application of one single unique registration key obtained from RisingRoad.

Just like one copy of a book can't be read by two different people in two different places at the same time, neither can one copy of Foxhound be executed on two different computers at the same time. (Unless, of course, this License Agreement has been violated, or a Multiple-Copy License has been obtained as explained below.)

2. Simple Bulk Purchase

A simple bulk purchase involves the purchase of multiple registration keys where each registration key is used to activate a separate copy of Foxhound, and each resulting copy meets the definition of "one copy of Foxhound" given earlier. This is analogous to the bulk purchase of multiple copies of a book. Simple bulk purchases are covered by this License Agreement; they do not require a Multiple-Copy License.

3. Use on a Network or the Internet

One copy of Foxhound may be executed on a computer attached to a local area network and/or the internet, with multiple users accessing the single Foxhound database from browsers running on different computers. The "just like a book" analogy begins to weaken at this point, but it still applies if you think of more than one person reading the same book over someone else's shoulder... it's still one copy of the book, and one copy of Foxhound executing.

4. Multiple-Copy License

A Multiple-Copy License involves the purchase of the right to make a limited number of identical copies after one original copy of Foxhound has been activated with one registration key, and to run these identical copies on different computers at the same time. This is analogous to making multiple photocopies of a book, an operation that is normally forbidden by the book's copyright terms. A Multiple-Copy License requires express written permission from RisingRoad, separate from this License Agreement.

5. Further Explanation of Copyright Law and the Scope of This License Statement

You may not download or transmit your copy of Foxhound electronically (either by direct connection or telecommunication transmission) for the purpose of executing it on multiple computers at the same time, except as may be specifically allowed by a Multiple-Copy License.

You may transfer all of your rights to use your copy of Foxhound to another person, provided that you transfer to that person (or destroy) all of the software and documentation provided in this package, together with all copies, tangible or intangible, including copies in RAM or installed on a disk, as well as all back-up copies. Remember, once you transfer your copy of Foxhound, it may only be executed on the single computer to which it is transferred and, of course, only in accordance with copyright law and international treaty provisions.

Except as stated in this paragraph, you may not otherwise transfer, rent, lease, sub-license, time-share, or lend the Foxhound software or documentation. Your use of Foxhound is limited to acts that are essential steps in the use of Foxhound on your computer as described in the documentation. You may not otherwise modify, alter, adapt, merge, decompile or reverse-engineer Foxhound, and you may not remove or obscure RisingRoad copyright notices.

6. Disclaimer of Warranty

The software is licensed "as is". You bear the risk of using it. RisingRoad gives no express warranties, guarantees or conditions. RisingRoad excludes the implied warranties of merchantability, fitness for a particular purpose and non-infringement.

[ Top ]

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

Answer: You can always install a new build of Foxhound on top of an old one, and your data will be copied and upgraded.

However, in some cases you may be required to provide a new registration key after the data upgrade and installation is complete:

A new Evaluation build can be installed on top of an old Evaluation build without providing a registration key.
A new Evaluation build will not change the expiry date.
Only one Evaluation period is allowed per customer.
A new Basic build can be installed on top of an old Basic build, and a new Extended build can be installed on top of an old Extended build, without providing a registration key, until the "free upgrade" period ends.
The end of the current free upgrade period has not been announced. When such an announcement is made, you may be able to use your "Original Full Build Number" to determine if you need a new registration key.
Your Original Full Build Number is shown on the About page.
An Evaluation copy may be upgraded to Basic or Extended, and a Basic copy may be upgraded to Extended, at any time by providing a registration key on the About page. This process does not require you to install a new build.

If you accidentally install a new build that requires a new registration key, and you don't have one (and don't want to get one), you can restore and resume using your old Foxhound database. See How do I restore the old build of Foxhound after installing a new build?

[ Top ]

Question: What happens when a copy of Foxhound expires?

Answer: If your installed Evaluation copy of Foxhound expires, you will be still able to view the History portion of the Monitor Database feature, as well as view your Foxhound Options and Alerts Criteria settings. However, the Monitor Database process will not gather any new samples and by implication the Alert process will cease to function. Also, the Display Schema feature will be disabled.

Other limitations may be applied to the installation of new builds; e.g., the end of the "Free Upgrade" period. These limitations are not yet fully defined, but they will take the form of requiring you to provide a new registration key to activate the new build. This is not the same as expiration which prevents full use of your old build: if you don't have a new registration key for the new build, you can always go back to your old build.

[ Top ]

Question: What's new in Foxhound 1.2?

Answer:
What's Cool (in Foxhound 1.1)
What's New (in Foxhound 1.2)

Foxhound Alerts tell you if something bad is happening:

can't connect,

slow response,

blocked connections,

high CPU,

I/O bottleneck,

and 24 other symptoms.


Now you can use Gmail to send the Alerts as well as receive them.
See: How do I tell Foxhound to send Alert emails via the Gmail SMTP server smtp.gmail.com?

Foxhound can monitor up to 100 databases.
Now it's easier to manage large numbers of Monitor sessions:

The hard-to-find "Alerts Criteria" page has been redesigned and elevated as the "Monitor Options" page.
See: The Monitor Options Page.

The Default Settings can be directly edited on the Monitor Options page, separate from the options for any particular target database.
See: Monitor Options - Switch Display.

The Force Default Settings On All Targets button on the Monitor Options page lets you publish new settings to all the targets.
See: Save And Restore Alerts Criteria Defaults.

The Manage Multiple Monitor Sessions feature lets you specify batches of target databases, and the Start and Stop All Sessions buttons let you turn sampling on and off for each batch.
See: Manage Multiple Monitor Sessions.

The Monitor tab on the Foxhound Menu page shows all the target databases at a glance.
The Monitor tab is now easier to use, and more informative:

The Disable Refresh and Enable Refresh buttons make it easier to scroll down to look at something.

The lists of targets and outstanding Alerts have been vertically squished so you don't have to scroll down so far when you've got lot of targets.

More "at a glance" columns have been added:

Active Alerts count, with a link down into the Alerts list

Conns

Waiting Req

Locks Held, Blocked Conns

CPU Time

Temp Space

Disk Reads, Writes

The Start All Sampling and Stop All Sampling buttons let you turn sampling on and off for all the targets.

See: The Monitor Tab.

The History page shows all the details for an individual database at a glance.
You can what happened overnight, yesterday, as far back as you want,

even the connections,

and the connections can be sorted on any of the columns, like "CPU Time" and "Locks Held".

You can also see all the blocked connections:
Who's blocked?

What are they waiting for?

How long have they been waiting?

Who's holding the locks?

What kind of locks are they?

What tables?

What rows?

How long has it been since they last did a commit?


Scrolling through gigabytes of data used to be slowwwww, like continental drift, now it's faster. New scroll amounts have been added (500 samples and 3 hours):
� Newest � 500 � 100 � 20 � 1 sample 1 sample � 20 � 100 � 500 � Oldest � � Month � Week � Day � 3 Hours � 1 Hour 1 Hour � 3 Hours � Day � Week � Month �
The "Freeze Frame Heights" button lets you resize and freeze the History page frames so they don't reset ("Grrr!") every time you scroll.
See: The History Page.

It's your data: Foxhound lets you run adhoc queries.
New views have been added for adhoc reporting. A separate read-only "Adhoc Schema" database lets you see what the views and underlying tables look like. New connection-level columns have been added to make queries easier to write:
LockRowID BIGINT NULL blocked_connection_count BIGINT NOT NULL DEFAULT 0 current_req_status VARCHAR ( 100 ) NOT NULL DEFAULT '' cache_satisfaction DECIMAL ( 30, 0 ) NOT NULL DEFAULT 0.0 time_connected BIGINT NOT NULL DEFAULT 0 total_waits BIGINT NOT NULL DEFAULT 0 waiting_time DECIMAL ( 30, 6 ) NOT NULL DEFAULT 0.0 transaction_running_time BIGINT NOT NULL DEFAULT 0 time_since_last_request BIGINT NOT NULL DEFAULT 0 index_satisfaction DECIMAL ( 30, 0 ) NOT NULL DEFAULT 0.0
Except for LockRowID, all the new columns contain values that Foxhound used to calculate only when the data was displayed on the Monitor and History pages; now these values are calculated once and stored permanently.
See: How do I run adhoc queries on the Foxhound database?

Foxhound automatically copies and upgrades all of your data when you install a new version. The upgrade process handles all the schema differences between the old and new versions of the Foxhound database, no matter what the old and new versions are (well, as long as the new version isn't older than the old version :).
The data upgrade process now runs faster, even though it has to work harder in version 1.2 to add all those new columns. You also have control over how much data to upgrade:

The default is FOXHOUND1UPGRADE = ALL to copy all the data from your old Foxhound database to the new one.

If you choose FOXHOUND1UPGRADE = OPTIONS during the installation process, Foxhound will copy everything except the Monitor samples. When you start Foxhound again, all the old sample data will be gone but sampling will start again right away (assuming it was running before you installed the new version).

If you want to save the Monitor samples recorded since a particular date, specify FOXHOUND1UPGRADE = yyyymmmdd.

To save the samples recorded during the past n days, use FOXHOUND1UPGRADE = n.

What's really cool about the new upgrade process is you can use it to purge, shrink and reorganize the Foxhound database: just reinstall the same version of Foxhound with FOXHOUND1UPGRADE = yyyymmmdd or FOXHOUND1UPGRADE = n.
See:

How do the different FOXHOUND1UPGRADE values work?
How do I shrink the size of the Foxhound database?

Foxhound supports target databases running all versions of SQL Anywhere from 5.5 through 12.0.1.
Good news, bad news:

Foxhound still supports all those old target databases, back to 5.5.05.2787.

Foxhound itself now runs on SQL Anywhere Version 12.0.1.

Foxhound will use the 64-bit version of SQL Anywhere 12.0.1 if it is installed. Previously, Foxhound ran only on the 32-bit version of SQL Anywhere 11.0.1.
See: How do I tell if Foxhound is running on the 32-bit or 64-bit version of SQL Anywhere?

You can force Foxhound to use the 32-bit version of SQL Anywhere by setting the FOXHOUND1BIN environment variable to Bin32... sometimes, it's just easier to do that than to try to figure out what's going wrong with ODBC and a legacy target database.
See: How do I start Foxhound with the 32-bit version of SQL Anywhere when both the 32-bit and 64-bit versions of SQL Anywhere are installed?

Bad news: Foxhound requires SQL Anywhere 12.0.1.3298 or later to run. And it still only runs on Windows. But none of that affects your target database: as long as Foxhound can establish an ODBC connection to your database, it can monitor the performance and display the schema.
See: Requirements.

More "What's New"...

The look-and-feel of the Foxhound Options page has changed to match the new improved Monitor Options window.
See: The Foxhound Options Page.
A single global "Enable Emails" setting has been added to the Foxhound Options page in case you want to turn off an accidental "alert storm".
See: Foxhound Options - Global Overrides.

New shortcuts have been added:

start - All Programs 
   Foxhound1
      Start Foxhound via Chrome
      Tools 
         Backup Foxhound Transaction Log
         Start Foxhound via Chrome - debug

See:
How do I start Foxhound?
How do I backup my Foxhound database?

Exception handling has been improved to allow Foxhound to continue operating after receiving bad data from a target database.
See: How do I report unexpected errors and exceptions?
The thirty-day Evaluation period can now be extended: just get a Evaluation Renewal key from breck.carter@gmail.com.
See: How do I get a copy of Foxhound?

[ Top ]

Question: What is the history of Foxhound?

Answer: Work on the original version of Foxhound began in March 1998. Back then it was called the RisingRoad Dictionary, and it used Oracle PL/SQL scripts to read the catalog views and generate static HTML containing the CREATE TABLE text for each table in a separate page. These pages included hyperlinks for rapid navigation up and down the parent-child foreign key hierarchy.

The original target audience was application programmers working with an enormous Oracle database at the Princess Margaret Hospital in Toronto. The database was so big and complex that graphical diagrams produced by tools like ERwin were virtually unusable by the programmers.

Graphical tools don't scale well; that is just as true today as it was back in 1998. Following foreign key chains on a diagram is very difficult when there are hundreds or thousands of tables, and any attempt to include the level of detail necessary for a programmer (physical data types and constraints for every column) instantly makes a diagram so large it won't fit on any wall let alone a desk. Subsetting a diagram never seems to work; it always seems to leave out stuff the programmer needs to know.

On the other hand, a text-based display plus hyperlinks and the browser's Back and Forward buttons are ideal for navigating a large database layout... and there's no shortage of screen real estate when you're showing one table at a time, even with all the physical details included.

Foxhound then went through a stage as a multi-platform (Oracle, SQL Server, DB2, SQL Anywhere) documentation tool with the addition of table- and column-level comments stored in its own database (SQL Anywhere).

Eventually, comments were dropped (little demand), as was support for multiple target platforms (too difficult), and Foxhound became a SQL-Anywhere-centric tool. SQL Anywhere's built-in HTTP server made it possible to display HTML on the fly rather than generate static HTML files that rapidly become out of date.

Over the years Foxhound has gradually evolved into a consultant's tool for investigating a client's database: how many tables, what do they look like to a programmer, what are the relationships, how do I get there from here. Foxhound grew to answer questions like how many rows, how much table/index/extension space is this table taking up, what's the average row size in terms of disk usage, where are all the database files and how badly fragmented are they.

The concept of "curiosities" was added: this database doesn't have any clustered indexes, that table doesn't have a primary key, these columns have the same names but different data types, that foreign key has a cascading action, these database options have been changed from their default settings... and this database still has OPTIMIZATION_GOAL set to 'First-row' which might explain why that query takes three hours instead of three minutes.

Then, in early 2007, something really big happened to Foxhound: The "Display Schema" button was joined by "Monitor Database" and a dynamically refreshed HTML display showing what's happening inside the server. By the summer of 2009 the Monitor was producing Alerts and All Clear messages about the availability of your target database and twenty-eight other conditions that fall short of an actual crash.

[ Top ]

Question: What environment variables are used by Foxhound?

Answer:

FOXHOUND1 is very important. It is set by the Foxhound InstallShield setup program to contain the drive and path of the folder where Foxhound is installed. It is then used in most of the Windows command files that are executed by the Foxhound shortcuts. For example, the "Start - Foxhound1 - Start Foxhound via Chrome" executes the $start_foxhound1_chrome.bat file which contains the command CD /D "%FOXHOUND1%".

Normally you do not have to enter or change the FOXHOUND1 environment variable, but if you do, here's how:

Start 
  - Control Panel 
    - System 
      - Advanced system settings 
        - Environment Variables...

FOXHOUND1BIN is optional and rarely used. You can set it to Bin32 if you want to start Foxhound using the 32-bit version of SQL Anywhere 12 even if the 64-bit version is available. Values other than Bin32 have no effect. The default action (if FOXHOUND1BIN is not set to Bin32) is to start Foxhound using the 64-bit version of SQL Anywhere if it is installed, otherwise use the 32-bit version.

No automatic process sets or changes the FOXHOUND1BIN environment variable, it's all up to you:

Start 
  - Control Panel 
    - System 
      - Advanced system settings 
        - Environment Variables...

FOXHOUND1UPGRADE is optional and rarely used. If it is set, it is used as the initial value for the FOXHOUND1UPGRADE setting in the post-setup process the next time you reinstall or upgrade Foxhound.

The post-setup process will prompt you to provide a different value if one is desired:

******************************************************************
*** 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=

The default action (if FOXHOUND1UPGRADE is not set to any value) is to use the the value ALL as the initial value, which you can change as shown above; see How do the different FOXHOUND1UPGRADE values work?

No automatic process sets or changes the FOXHOUND1UPGRADE environment variable, it's all up to you:

Start 
  - Control Panel 
    - System 
      - Advanced system settings 
        - Environment Variables...

[ Top ]

Question: What HTTP port should I use for Foxhound?

Answer: Port 4950 is officially registered to the "Sybase Server Monitor" which is the SQL Anywhere Monitor that ships in the box with SQL Anywhere. If you're not already running the SQL Anywhere Monitor on that port, consider using 4950 for Foxhound.

Alternatively, consider using one of the "Dynamic and/or Private Ports" in the range 49152 through 65535.

[ Top ]

Question: What happened to Foxhound Options - Export Samples?

Answer: The Foxhound Options - Export Samples feature has been replaced with the ability to perform adhoc queries against the Foxhound database via dbisql and other client software.

For more information see How do I run adhoc queries on the Foxhound database?

[ Top ]

Question: What is the foxhound1.db ... .ORIGINAL_COPY file?

Answer:

It is a copy of the foxhound1.db file as delivered; i.e., before anything was copied from the old Foxhound database including the activation status.

It is created in foxhound1\setup folder by the $post_setup.bat command file after the InstallShield setup runs but before the post-setup data upgrade process runs.

This page was last generated on February 26, 2012.

Foxhound 1.2 FAQ Home Foxhound Home RisingRoad Breck.Carter@gmail.com