Help for Foxhound 4.0.4740a
Table of Contents [RisingRoad]
The "Foxhound" home page is called the Foxhound Menu because it lets you choose which target database you want to work with.
1.1 The Foxhound Menu Menu
Every page has a menu line, even the Foxhound Menu :)
The New Menu link opens the Foxhound Menu page in a new browser window or tab. This link appears on every Foxhound page to make it easy to look at multiple databases at the same time.
The Foxhound Options link opens the Foxhound Options page in a new browser window or tab.
The Monitor Options link opens the Monitor Options page in a new browser window or tab. That page lets you enable and disable different alerts, change the conditions under which alerts are issued and manage multiple Monitor sessions using a tab-delimited file of connection strings.
The button is a context-sensitive link to this Help topic. This button appears in many locations, each of them a link to a different Help topic in this frame.
The About link opens the About Foxhound page in a new browser window or tab.
The DSN tab lets you pick a target database by using an ODBC Data Source.
If you don't have a DSN, and you don't want to create one, try using the String tab instead.
The Choose a DSN: drop-down list lets you pick which DSN you want from all the User and System DSNs recorded in the Windows registry.
Foxhound turns off AutoStart and AutoStop processing as follows:When Foxhound connects to the target database it uses a connection string that looks like this, where xxx is the DSN you have specified:
or this if you have provided a user id yyy and password zzz:DSN=xxx; AutoStop=NO; AutoStart=NO; ConnectionName=Foxhound-pnnnThe AutoStop=NO; AutoStart=NO; ConnectionName=Foxhound-pnnn values override any values specified inside the DSN. The nnn value will be a number 001, 002, etc.UID=yyy; PWD=zzz; DSN=xxx; AutoStop=NO; AutoStart=NO; ConnectionName=Foxhound-pnnnIf you want AutoStop and/or AutoStart processing, use the String tab to connect instead of the DSN tab.
The User Id: and Password: fields are optional; you don't need to fill them in if values are stored in the DSN itself.
Check Include system tables if you want the Display Schema page to include the SQL Anywhere catalog tables and views; e.g., ISYSTAB and SYSTABLE.
The button connects to the target database and opens the Display Schema page in the current browser window or tab.
The button opens the Monitor Database page in the current browser window or tab. If a sampling session already exists for this DSN, sample data from that session will be displayed. If not, Foxhound will start a new sampling session and display that data.
The button tells Foxhound to include non-SQL Anywhere DSNs in the Choose a DSN: drop-down, and excludes them again.
The button starts the Windows ODBC Data Source Administrator program so you can edit and create DSNs.
This button is disabled if the Foxhound engine is not running locally. Foxhound can only use the ODBC DSNs that are stored on the same machine that's running the Foxhound engine, so that's where you have to go to run the ODBC Administrator.This button may not work properly if the Foxhound engine is running as a service on the local computer. In general, services cannot launch interactive user interfaces; e.g., the ODBC Administrator interface.
The String tab lets you pick a target database by specifying the SQL Anywhere connection string. Foxhound always uses ODBC to connect to the target database, but that doesn't mean you need to create a DSN, and this tab makes a DSN-less connection possible.
... but, if you always use DSNs to connect to your database, you probably don't need to use the String tab at all.
The Choose a connection string: drop-down list lets you pick which connection string you want to use. Connections strings are stored in the Foxhound database, and several samples are delivered in the initial setup.
The Enter or edit the connection string... box lets you create, edit and delete your connection strings.
The Name: field lets you specify a name to uniquely identify this connection string in the Foxhound database. Connection string names are separate from DSN names so you can use the same names if you want.
The String: field lets you fill in the connection parameters.
Foxhound changes the default settings for AutoStop and AutoStart from YES to NO, and provides a default connection string name, by appending the following connection parameters to the end of the string you provide (where nnn is a number 001, 002, etc):If you provide different values for these parameters in the string you provide, your values will be used because that's the way connection strings are processed: the first value for any parameter is the one that is used.AutoStop=NO; AutoStart=NO; ConnectionName=Foxhound-pnnnHowever, that rule does not apply if you specify a DSN=xxx parameter and code your connection parameter values inside the DSN: the values specified in the outer connection string, including the values appended by Foxhound will be used instead.
Tip: Foxhound comes with several pre-defined connection strings, and later upgrades may add more. Feel free to delete or edit these strings as you wish; depending on how your computer is set up you may have to change some of them so they will work properly.Tip: To see all the views and tables available for adhoc reporting, select "Foxhound 4 Adhoc Schema - autostart and connect" and click on the Display Schema button.
The button clears the Name: and String: fields.
The button displays several examples of connection parameters, and hides them again. Click on an example to paste it into the String: field.
Here's are the examples and how you might use them:ENG=ddd; DBN=ddd; UID=dba; PWD=sql; DRIVER=SQL Anywhere Native; - Use this string to connect to a target database using the ODBC driver version that matches the target server version. ENG=ddd; DBN=ddd; UID=dba; PWD=sql; DRIVER=SQL Anywhere 12; ENG=ddd; DBN=ddd; UID=dba; PWD=sql; DRIVER=SQL Anywhere 16; ENG=ddd; DBN=ddd; UID=dba; PWD=sql; DRIVER=SQL Anywhere 17; - Use these strings to connect to a target database using a specific ODBC driver version. LINKS=TCPIP(HOST=192.168.1.101; PORT=2638; DoBroadcast=NONE); - Choose from these parameters when dealing with connectivity issues. START=C:\Program Files\SQL Anywhere 12\bin64\dbsrv12.exe -c 100M; START=C:\Program Files\SQL Anywhere 16\bin64\dbsrv16.exe -c 100M; START=C:\Program Files\SQL Anywhere 17\bin64\dbsrv17.exe -c 100M; DBF=C:\path\ddd.db; AUTOSTART=YES; - Choose from these parameters to auto-start the target database when Foxhound connects to it.
The button saves the String: field in the Foxhound database with Name: as the identifier. This will do an update or insert depending on whether Name: already exists or not.
The button deletes the connection string identified by Name: as long as no Database Monitor samples have been collected for this target database.
If the connection string appears on the both the String tab and Monitor tab of the Foxhound Menu page (which means samples have been gathered for this target database) the Delete button on the String tab won't do anything. In this case go to the Monitor tab and click on the Delete link (to delete the samples) then go to the String tab and press the Delete button (to delete the connection string).
Tip: To rename an existing connection string, type the new Name and Save the string, then Choose and Delete the string with the old name.
The Password: field is optional; you don't need to fill it in if your connection string includes a value.
Check Include system tables if you want the Display Schema page to include the SQL Anywhere catalog tables and views; e.g., ISYSTAB and SYSTABLE.
The button connects to the target database and opens the Display Schema page in the current browser window or tab.
The button saves the connection string and then opens the Monitor Database page in the current browser window or tab. If a sampling session already exists for this connection string, sample data from that session will be displayed. If not, Foxhound will start a new sampling session and display that data.
The Monitor tab lists all the sampling sessions that have been created. When this tab is displayed, it is refreshed every 10 seconds with the most recent data. It is also refreshed whenever you switch to it from the DSN or String tab.
The button starts all the sampling sessions in the list that aren't already running.
If there are a large number of sampling sessions, it might take a while for them to all start.The Start All Sampling button will not affect any sampling sessions that have a Sample Schedule in effect. If sampling is under the control of a Sample Schedule, you can't stop and start sampling manually, you have to adjust (or turn off) the schedule on the Monitor Options page.
The button stops all the sampling sessions in the list that are currently running.
The Stop All Sampling button will not affect any sampling sessions that have a Sample Schedule in effect. If sampling is under the control of a Sample Schedule, you can't stop and start sampling manually, you have to adjust (or turn off) the schedule on the Monitor Options page.
The button immediately updates the information displayed on this tab without waiting for the regular refresh.
If the display is paused but sampling sessions are running, you can press Refresh Display to show the most recent information without restarting the automatic refresh process.The (number) in parentheses in the Refresh Display button tells you how many times this page has been refreshed.
The button stops the Monitor page from being refreshed every 10 seconds, and the button starts it again.
Neither button affects the background sampling process one way or the other. For example, if sampling sessions are running and you press Disable Refresh and later press Enable Refresh, the displayed data "catches up" with the most recent information.
The ID column shows the sampling_id primary key value that uniquely identifies each sample session in the Foxhound database. This key is useful for writing adhoc queries when you have more than one target database.
The Target Database column displays the DSN: and String: names used to identify the sampling sessions.
Each name in the list is a link which opens the Monitor page for the corresponding target database in a new browser window or tab.
The Open Page column offers links to three different Foxhound pages:
The Monitor column offers links to perform three different actions on the corresponding database:
The (schedule in effect) link may appear instead of Start, Stop and Delete. If sampling is under the control of a Sample Schedule, you can't stop and start sampling manually, you have to adjust (or turn off) the schedule on the Monitor Options page.
The Cancel link may appear instead of Stop. The Cancel button lets you stop further attempts to start or re-start the sampling session. If Foxhound can't connect to the target database, it will keep trying forever, unless you press Cancel or the connection timeout period is exceeded. See the Foxhound Options page for more information on connection timeouts.
This takes effect immediately, and is permanent; the sample data is no longer available for display. Also see the Foxhound Options page for more information on purging old sample data.Note: The phrase "is permanent" means there is no "cancel" or "undo" facility. It doesn't mean you can't ever gather samples for this database again; you just have click on the Monitor Database button to start another sample session.
The Monitor Status column tells you if everything is OK with the sampling session, or what kind of problem occurred. A dash "-" is displayed when the session was stopped with the Stop button.
The Active Alerts column lets you know if any Alerts are currently in effect (not yet All Clear or Cancelled) for this database. Values in this column are links that let you jump down to the corresponding Active Alerts... section at the bottom of this page.
Each database with one or more Alerts in effect (not yet All Clear or Cancelled) will have a corresponding Active Alerts... section at the bottom of this page. Each Alert has a link to open a History page for this database showing the corresponding Alert entry.
The Heartbeat column shows the elapsed time for the most recent "heartbeat" or "canarian" query SELECT * FROM DUMMY. This number should be very small, often less than 1s.
The Unsch Req column shows the number of requests that were waiting to be processed.
The Conns column shows how many connections to the target database exist.
The Blocked column shows how many connections to the target database are blocked.
The CPU Time column shows the percent used during the preceding interval.