Problem
In large estates, the iQSonar user interface can sometimes be slow to respond and/or display so much information as to be unwieldy to use. In these circumstances it can be useful to run diagnostic queries against the database directly rather than attempting to rely only on the iQSonar UI to discover why certain targets were not scanned and to make any needed changes to the scan engine configuration or to the targets to enable them to be scanned. As these queries rely on database tables in iQSonar which are not designed to be exposed to end users, some of the queries only work on certain versions of the product, and may need to be adapted due to changes between different versions of the scan engine.
Prerequisites
In order to use these scripts, you will need credentials to log in to the SQL server that hosts the iQSonar database. You will require permissions to run queries and, in some cases to execute stored procedures.
...
| Warning |
|---|
These queries work with iQSonar releases up to and including Fu R3.Some of them do NOT work with iQSonar Gwynn R1 or later due to changes to the history.t_ConnectionHistory table. |
...
Changes were made to some underlying tables in Gwynn R1 and Gwynn R2 to reduce the amount of history saved as the diagnostic information can grow. In the Gwynn R3 release the option to preserve or delete this diagnostic can be selected in the user interface. Instructions on how to keep the history data can be found on this page. |
...