|
|||||||||||
|
|
|||||||||||
How?How do I do a quick reinstall and reactivation of Foxhound?How do I figure out what went wrong during an installation? How do I find my OFSS samples? How do I find the post_setup_trace.txt file? How do I get a copy of Foxhound? How do I get a registration key for Foxhound? How do I get an activation key for Foxhound? How do I get an HTTP request log for Foxhound? How do I get the new value of the FOXHOUND5 environment variable to show up after Foxhound is installed? How do I install a new build of Foxhound 5? How do I install a new version of Foxhound? How do I install Foxhound? How do I install version 17 of SQL Anywhere on the same machine used to run an earlier version of SQL Anywhere? How do I make Foxhound web pages available on the internet? How do I make the post-setup process run faster when a large Foxhound database is being upgraded? How do I move an existing Foxhound installation to a different location? How do I move Foxhound to a different disk drive? How do I move the Foxhound database to a different location? How do I move the Foxhound transaction log to a different physical disk drive? How do I move the SQL Anywhere temporary file for Foxhound to a different physical drive? How do I protect the security of my target database? How do I quickly shrink the Foxhound database? How do I read the Foxhound exception messages? How do I reinstall an earlier build of Foxhound? How do I reinstall Foxhound? How do I relocate the Foxhound database from the default installation location? How do I remove Foxhound from my system? How do I rename a connection string on the String tab of the Foxhound Menu page? How do I renew the Rental Edition of Foxhound 5? How do I report unexpected errors and exceptions? How do I reset my Foxhound database to empty, without reinstalling? How do I restore the old build of Foxhound after installing a new build? How do I run the Foxhound "unsetup" process? How do I "Save As" an existing connection string to a new string with a different name on the String tab of the Foxhound Menu page? How do I see Foxhound diagnostics, errors and exceptions? How do I shrink the size of the Foxhound database? How do I specify the HTTPS transport-layer security for Foxhound? How do I stop the "User Id:" and "Password:" from being redisplayed on the Foxhound Menu page? How do I tell Foxhound to use an HTTP port other than 80? How do I uninstall Foxhound? How do I "unsetup" Foxhound? How do I upgrade Foxhound from one edition to another? How do I upgrade from the Basic Edition of Foxhound 5 to the Extended Edition? How do I upgrade from the Rental Edition of Foxhound 5 to the Basic Edition? How do I upgrade from the Rental Edition of Foxhound 5 to the Extended Edition? How do I upgrade to a new build of Foxhound 5? How do I upgrade to a new version of Foxhound without losing any of my data? How do I upgrade to Foxhound 5? How many target databases can one copy of Foxhound monitor? How much disk space does Foxhound need? How much overhead does the Foxhound connection add to the target database? rroad_OFSS_load rejected ... |
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I figure out what went wrong during an installation?
Question: How do I find the post_setup_trace.txt file? Answer: If the problem occurred during the post-setup part of the Foxhound installation, a complete record of everything that happened may be found in the following files: which are located here on Windows 10:$$BUILD_NUMBER.txt $$FOXHOUND5UPGRADE.txt $post_setup.bat diagnostic_01.txt diagnostic_02.txt diagnostic_03.txt diagnostic_04.txt diagnostic_05.txt find1.txt find2.txt old_foxhound1_debug.txt old_foxhound1_debug_startup.txt post_setup_trace.txt C:\ProgramData\RisingRoad\Foxhound5\setup\post_setup_trace.txt If you need help, zip them up and send them to Breck.Carter@gmail.com.
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I find my OFSS samples?
Question: rroad_OFSS_load rejected ... Question: What happened to my OFSS samples? Answer: If you don't see your OFSS samples in the Foxhound Sample History page, the OFSS batch files may have been rejected. To see the reason(s) why, look for messages in the Diagnostics section of the Foxhound Options page.
Here is an example of 4 diagnostic messages in reverse timestamp order, showing one "The error was detected" message followed by 3 "The file is now located here" messages: When OFSS batch files are rejected, they are moved to the "rejected" subfolder. For example, if you called rroad_OFSS_load() like this
then your files may have been moved to this location
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I get a copy of Foxhound?
Question: How do I get a registration key for Foxhound? Question: How do I get an activation key for Foxhound? Answer: Foxhound comes in two parts: An Installshield setup file and a registration key. The setup file can be downloaded from the Foxhound home page.
For more information about editions, see What are the differences among the different editions of Foxhound: Rental, Basic and Extended? For more information about activation keys, see What are the differences among all the activation keys?
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I get an HTTP request log for Foxhound?
Answer: At the very least, you must add both the dbn=f and the log=filespec network protocol parameters to the dbsrv17 -xs http(...) parameter when starting Foxhound. Don't forget the dbn=f parameter; it's not documented as being required, but if you leave it out nothing will be written to the log file. Here is an excerpt from the C:\ProgramData\RisingRoad\Foxhound5\$start_foxhound5_engine.bat command file showing a modified -xs http(...) parameter:
Here's what the resulting output file C:\temp\foxhound_http_log.txt looks like:
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I install a new build of Foxhound 5?
Question: How do I upgrade to a new build of Foxhound 5? Answer: This article describes how to upgrade an existing copy of Foxhound 5 to a new build of Foxhound 5; e.g., Update 1.
First, you must run the Foxhound 5 "unsetup process" There are three ways to run the unsetup process:
Second, install the new build of Foxhound 5. Here's how to install Foxhound 5 without losing any of your data:
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I install a new version of Foxhound?
Question: How do I upgrade to a new version of Foxhound without losing any of my data? Question: How do I upgrade to Foxhound 5? Answer: Here's how to install Foxhound 5 without losing any of your data stored in Foxhound 3 or 4:
Caution: If you are running Foxhound as a service, stop the service before installing the new version. The installation process needs to stop and restart the existing Foxhound database, and it probably won't be able to do that if it's already running as a service. Caution: If you are using the Windows Vista or Windows 10 Task Scheduler to take regular backups of your Foxhound database using the $backup_foxhound5.bat file you should reboot your computer after installing a new version of Foxhound.
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I install Foxhound?
Answer: Step 1: Download the Foxhound Installshield setup file from the Foxhound home page. Step 2: Run setup file; here's what you should see:
Step 3: Let the InstallShield process do it's thing: Step 4: In the case of a fresh installation the "post-setup" process runs automatically: Step 5: When the setup is finished, press OK to start the Foxhound: Step 6: The Foxhound Activation page will appear in the browser window:
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I install version 17 of SQL Anywhere on the same machine used to run an earlier version of SQL Anywhere?
Answer: Follow the normal process for installing SQL Anywhere 17; version 17 of SQL Anywhere can coexist on the same computer as all other versions from 6 and up. There is one caveat, however: The SQL Anywhere 17 installation modifies the Windows PATH environment variable. If you have been relying on the PATH to determine where SQL Anywhere utilities such as dbbackup.exe and dbvalid.exe are located, your Windows command lines and batch files may start executing the version 17 copies of those utilities instead of the version you want. Either change the PATH variable, or modify your Windows command lines to explicitly specify the folder containing the utilities. Each version of SQL Anywhere comes with its own environment variable that makes it easier to code commands; here's an example of how to use the SQLANY10 environment variable to execute the version 10 copy of dbvalid.exe:
"%SQLANY10%\win32\dbvalid.exe" -c "ENG=ddd10;DBN=ddd10;UID=dba;PWD=sql" -d -o dbvalid_log_ddd10.txt Here's a list of the environment variables for each version:
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I make Foxhound web pages available on the internet?
Answer: By default the built-in Foxhound web server is internet-ready so if the computer running Foxhound is visible on the internet then so are the Foxhound web pages. For example, if the Foxhound engine is started on a computer with IP address aaa.bbb.ccc.ddd, you can display the Foxhound pages on another computer by specifying the following URL in a browser: http://aaa.bbb.ccc.ddd/
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I make the post-setup process run faster when a large Foxhound database is being upgraded?
Answer: Try using the SATMP environment variable to put the SQL Anywhere temporary file on a different physical disk drive.
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I move Foxhound to a different disk drive?
Question: How do I move an existing Foxhound installation to a different location? Question: How do I relocate the Foxhound database from the default installation location? Answer: This example shows how to move an existing Foxhound installation from C:\ProgramData\RisingRoad\Foxhound5 to H:\FOXHOUND5.
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I move the Foxhound database to a different location?
Answer: Some customers require that software may be installed on the C: drive, for example, but updatable files (e.g., the Foxhound database) must be installed in a different location.
Here is an example that shows how the Foxhound database may be moved from the original installation folder
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I move the Foxhound transaction log to a different physical disk drive?
Answer:
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I move the SQL Anywhere temporary file for Foxhound to a different physical drive?
Answer: One method is to set the SATMP environment variable to specify the folder where SQL Anywhere will put all its temporary files:
Another method is to modify the dbsrv17.exe command line which starts Foxhound to include the -dt F:\data\SQL_Anywhere_temp option; this will only affect the temporary file associated with the Foxhound database: Here's the list of Foxhound command files which contain the dbsrv17.exe command:
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I protect the security of my target database?
Answer: One way to protect the security of your target database is to use the HTTPS protocol. For more information see How do I specify the HTTPS transport-layer security for Foxhound? Another technique is to create a new user id on the target database with no privileges other than CONNECT, and use that user id for Foxhound to connect: -- Run this command on the target database: GRANT CONNECT TO FOXHOUND IDENTIFIED BY SQL; -- Set up a connection string like this on the String tab of the Foxhound Menu: Name: ddd16 String: ENG=ddd16; DBN=ddd16; UID=FOXHOUND; PWD=SQL; DRIVER=SQL Anywhere 16; The Display Schema feature should work OK with the new "FOXHOUND" user id. The Monitor Database feature should also work, but Foxhound's own performance might suffer because Foxhound can't create the three high-performance procedures on the target database it needs to gather performance data efficiently; in this case the Monitor page will display "SPs are OK: NNN" instead of "SPs are OK: YYY". You can install those three procedures on the target database yourself; for step-by-step instructions see Help - Introduction - Connecting to Target Databases.
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I reinstall an earlier build of Foxhound?
Answer: The regular re-installation process will work for an earlier build. HOWEVER, the post-upgrade process will NOT copy the data from your current Foxhound database to the one that's being installed when the current installed build number is later than the one that's being installed. That means you lose your sample data and option settings, and it means you will have to activate Foxhound as if it were a brand new installation.
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I reinstall Foxhound?
Answer: To reinstall Foxhound, run the InstallShield setup. What you do next depends on which dialog box appears...
If you see a dialog box that looks like either of these, you have to run the Foxhound "unsetup" process first and then run the Foxhound InstallShield setup as described below:
The unsetup process will not delete your Foxhound database; for more information see Another version of this product is already installed.
If you see this dialog box, you can proceed with the reinstallation:
The post-setup process will ask how much data you want to preserve; just press Enter for ALL data: Post-Setup Process for Foxhound Version 5.0 *** Checking for a post-setup path parameter... *** A post-setup path parameter was provided... C:\ProgramData\RisingRoad\Foxhound5\ ******************************************************************* *** Foxhound 5.0.xxxx *** *** Here's where Foxhound is being installed: *** C:\ProgramData\RisingRoad\Foxhound5\ *** *** Starting the Foxhound 5,0.xxxx post-setup process... *** Creating foxhound5.db.5,0.xxxx.ORIGINAL_COPY... *** Checking for an existing Foxhound5 installation... *** ...yes, there is an existing Foxhound5 installation. *** Checking if the existing data should be upgraded... *** ...yes, the existing Foxhound5 data should be upgraded. ****************************************************************** *** PLEASE READ THIS, AND CONFIRM OR CHANGE ********************** ****************************************************************** *** *** "FOXHOUND5UPGRADE" specifies how much data is to be upgraded. *** *** 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. *** *** If you LIKE the current setting... *** FOXHOUND5UPGRADE=ALL which means upgrade all the data *** just press Enter. ****************************************************************** Current FOXHOUND5UPGRADE=ALL New FOXHOUND5UPGRADE= For more information about how FOXHOUND5UPGRADE works see Foxhound Help - FOXHOUND5UPGRADE.
Caution: If you are using the Windows Vista or Windows 10 Task Scheduler to take regular backups of your Foxhound database using the $backup_foxhound5.bat file you should reboot your computer after installing a new version of Foxhound.
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I remove Foxhound from my system?
Question: How do I uninstall Foxhound? Answer: First, stop the Foxhound database if it's running. You can do this by clicking on start - All Programs - Foxhound5 - Tools - Stop Foxhound Engine. Second, run the Foxhound "unsetup" process. There are three ways to do this:
Third, delete the Foxhound5 folder and all the files and subfolders. By default, Foxhound is installed in this location on Windows 10: C:\ProgramData\RisingRoad\Foxhound5
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I rename a connection string on the String tab of the Foxhound Menu page?
Answer: There is no "Rename" button; you have to copy-and-save and then delete:
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I renew the Rental Edition of Foxhound 5?
Answer: Step 1: Get 30-day Rental Key; see How do I get a copy of Foxhound? Step 2: Open the Foxhound About page. Step 3: Click on the "Renew or Upgrade Foxhound" button to open the Foxhound Activation page, and follow the instructions.
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I report unexpected errors and exceptions?
Answer: First, use the Foxhound Options - Diagnostics - Display Diagnostics button to see if there are any diagnostic messages associated with this problem. If so, use the Export Diagnostics button to copy the Foxhound diagnostic messages to a text file. Then, run this adhoc query to determine if Foxhound has captured any diagnostic dumps associated with those diagnostic messages; see How do I run adhoc queries on the Foxhound database?C:\temp\foxhound_diagnostics.txt
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I restore the old build of Foxhound after installing a new build?
Answer: Foxhound's executable code is stored together with Foxhound data inside the Foxhound database, so "restoring the old build of Foxhound" is the same as "restoring the old Foxhound database". The post-setup process creates a backup copy of your existing Foxhound database, and you can restore that copy by copying the foxhound.db and foxhound.log files as follows: On Windows 10, copy the foxhound.db and foxhound.log files from:C:\ProgramData\RisingRoad\Foxhound5\backup\previous_buildto:C:\ProgramData\RisingRoad\Foxhound5
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I run the Foxhound "unsetup" process?
Question: How do I "unsetup" Foxhound? Answer: There are three ways to run the Foxhound "unsetup" process:
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I "Save As" an existing connection string to a new string with a different name on the String tab of the Foxhound Menu page?
Answer: There is no "Save As" button; you have to change the name and then save:
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I see Foxhound diagnostics, errors and exceptions?
Question: How do I read the Foxhound exception messages? Answer: You can use Foxhound Options - Display Diagnostics to see messages recorded by Foxhound itself. Here is an example of a Foxhound exception message with an explanation of the different sections: exception id: 1, 2, 3... | date and time of the exception | | Foxhound build number | | | Foxhound connection number that detected the exception | | | | exception location within Foxhound code | | | | | diagnostic text: variable format target database id and name | | | | | | | 67 2011-11-11 11:49:08.768 Full Build 4013a 1000009471 701.a3(701eh1) Permission denied: Cannot CREATE PROCEDURE rroad_engine_properties. [5-ddd12] For more information about errors during Foxhound startup, try using one of the "debug" scripts; see Help - Introduction - Starting Foxhound - Method 2: Debug Startup.
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I shrink the size of the Foxhound database?
Answer: One method is to use the Foxhound upgrade process to purge old sample data by reinstalling Foxhound and specifying FOXHOUND5UPGRADE = yyyymmdd or nnn when the prompt appears during the post-setup process. For more information see How do I reinstall Foxhound? Even if you use a very old value of FOXHOUND5UPGRADE = yyyymmdd or a very large value of FOXHOUND5UPGRADE = nnn to copy all of the sample data, the Foxhound database will probably shrink somewhat because the reinstallation process removes free space. Another method is to let the purge process delete old and/or uninteresting sample data and then reinstall Foxhound as follows:
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I specify the HTTPS transport-layer security for Foxhound?
Answer: You can modify the Foxhound startup command line to specify RSA encryption and the HTTPS protocol as follows:
Here is an example of a dbsrv17.exe command line modified to allow only HTTPS access to Foxhound data using the sample certificate that comes with SQL Anywhere 17: "%SQLANY17%\%BIN%\dbspawn.exe"^ -f "%SQLANY17%\%BIN%\dbsrv17.exe"^ -c 25p^ -ch 50p^ -cr-^ -gk all^ -gn 220^ -gna 0^ -m^ -n foxhound5^ -o foxhound5_debug.txt^ -oe foxhound5_debug_startup.txt^ -on 1M^ -sb 0^ -ufd restart^ -x tcpip^ -xd^ -xs https(identity="%SQLANYSAMP17%\Certificates\rsaserver.id";identity_password=test;port=443;maxsize=0;to=600;kto=600)^ foxhound5.db^ -n f If you want to allow both HTTP and HTTPS access, specify both as follows: Here's the list of Foxhound command files which contain the dbsrv17.exe -xs option:-xs http(port=80;maxsize=0;to=600;kto=600),https(identity="%SQLANYSAMP17%\Certificates\rsaserver.id";identity_password=test;port=443;maxsize=0;to=600;kto=600)^
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I stop the "User Id:" and "Password:" from being redisplayed on the Foxhound Menu page?
Question: Why are the "User Id:" and "Password:" values redisplayed after I blank them out on the Foxhound Menu page? Answer: If you are using Firefox as your browser, try removing http://localhost from Foxhound's list of Saved Logins:
Options (gear icon)
Privacy & Security tab
Logins and Passwords section
Saved Logins... button
select Site http://localhost
Remove button
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I tell Foxhound to use an HTTP port other than 80?
Answer: You can edit one or more of the following Windows command files to specify a different HTTP port: Look for a line inside each command file that says this: -xs http(port=80;maxsize=0;to=600;kto=600)^and change the 80 to something else, like 12345: -xs http(port=12345;maxsize=0;to=600;kto=600)^Then, look for a line that says this: http://localhost/foxhoundand if you find it (all the "chrome", "firefox" and "ie" command files have it) change it like this: http://localhost:12345/foxhound
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I upgrade Foxhound from one edition to another?
Answer: It depends on what you want to do...
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I upgrade from the Basic Edition of Foxhound 5 to the Extended Edition?
Answer: Step 1: Get a Basic To Extended Key; see How do I get a copy of Foxhound? Step 2: Open the Foxhound About page. Step 3: Click on the "Upgrade Foxhound" button to open the Foxhound Activation page, and follow the instructions.
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I upgrade from the Rental Edition of Foxhound 5 to the Basic Edition?
Answer: Step 1: Get a New Basic Key; see How do I get a copy of Foxhound? Step 2: Open the Foxhound About page. Step 3: Click on the "Renew or Upgrade Foxhound" button to open the Foxhound Activation page, and follow the instructions.
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How do I upgrade from the Rental Edition of Foxhound 5 to the Extended Edition?
Answer: Step 1: Get a New Extended Key; see How do I get a copy of Foxhound? Step 2: Open the Foxhound About page. Step 3: Click on the "Renew or Upgrade Foxhound" button to open the Foxhound Activation page, and follow the instructions.
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How many target databases can one copy of Foxhound monitor?
Answer: A single copy of the Basic edition of Foxhound is limited to monitoring 10 target databases, and the Extended edition can monitor up to 100 target databases. However, the Extended Edition of Foxhound does not limit the number of separate copies of the Foxhound database that may be created and started using separate instances of SQL Anywhere on the same local network; see Help - Introduction - Starting Multiple Copies of Foxhound. Note: Here's what the End User License Agreement has to say... In the case of the Extended Edition, an unlimited number of copies of the Foxhound database may be created and started using separate instances of SQL Anywhere on the same local network, with the requirement that a separate Extended Edition registration key be purchased for each multiple of 10 copies of Foxhound started.
See also...
|
|||||||||||
|
|
|||||||||||
| [ Top ] | |||||||||||
|
Question: How much overhead does the Foxhound connection add to the target database?
Answer:
Note: This FAQ does not discuss the impact of running the Foxhound database on the same computer as the target database. If both databases are heavily loaded it is probably a good idea to move Foxhound to a different computer. Foxhound's overhead is approximately the same as a single persistent ODBC client-server connection that performs a small-to-medium (depending upon your point of view) amount of read-only query requests (three SELECTs) every ten seconds. The "Sample Times" column on the Monitor page shows how long it takes for Foxhound to do its work. Generally speaking, if Foxhound's overhead causes any problems, the target database is already in serious difficulty for other reasons. You can see the Foxhound connection in Foxhound itself; e.g., Foxhound-p001. It's not "zero impact" but it's not a heavy load either. The overhead goes up linearly with the number of other connections to the target database. For example, I have seen the CPU usage rise to 4% on a target database with 1000 idle connections; i.e., Foxhound was using 4% of the target server's CPU to gather information about 1000 connections every 10 seconds, even though those connections aren't doing anything. Foxhound's overhead affects the CPU and client-server communications only; Foxhound performs no database disk I/O on the target database. The Foxhound Monitor does almost all of its work inside its own SQL Anywhere server, so if you run that server on a different computer the impact on the target database server will be minimized. On the other hand, if you run Foxhound on the same box, and your target database is heavily loaded with a lot of connections, you can run into trouble. Historically, Foxhound itself has had internal performance problems from time to time, but there has never been clear evidence of Foxhound adversely affecting a *target* database. "Clear evidence" would be a target database that performs well without Foxhound, and performs poorly with Foxhound. One other factor has a large impact on Foxhound's own internal efficiency; here's a description: In the status area of the Monitor page (just below the buttons), there is an SP OK: field over to the right. SPs OK: YYY, NNN or some combination of Ys and Ns indicates whether or not Foxhound has deployed, and is using, these three stored procedure on the target database: rroad_connection_properties, rroad_database_properties and rroad_engine_properties. These stored procedures are used by Foxhound to improve the performance of the sampling process, but they are not absolutely required. If the user id that Foxhound uses to connect to the target database doesn't have the RESOURCE authority then Foxhound won't be able to CREATE these procedures on the target database. The source code for the three procedures is in the Foxhound5 folder (C:\ProgramData\RisingRoad\Foxhound5 on Windows 10) so you can see what they do yourself: rroad_connection_properties.sql rroad_database_properties.sql rroad_engine_properties.sql The effect of these procedures is to reduce the number of rows of data, and the number of bytes, transferred from the target database to Foxhound every 10 seconds. That, in turn, has a significant effect on Foxhound itself if there a large number of connections. When those procedures are not available on the target database, Foxhound calls these three system procedures on the target database every ten seconds: sa_conn_properties(), sa_db_properties() and sa_eng_properties(). For more information about these procedures see Help - Introduction - Connecting to Target Databases.
|
|||||||||||
|
|
|||||||||||
| This page was last generated on July 3, 2021. | Foxhound 5.0 FAQ Home Foxhound Home RisingRoad Breck.Carter@gmail.com | ||||||||||
