These options govern how AQT obtains the information on tables (and other objects) in your system. If AQT is unable to correctly display the tables in your system you could try changing some of these parameters, otherwise they should not be changed.
This determines whether table information is obtained from the System Tables or from the ODBC API calls. The default is System Tables (if that option is available for this database).
This parameter cannot be changed while you are currently signed onto a database.
For a further discussion on this see System-Table Query Feature.
If this option is selected, AQT will show the Favorites display when it opens the Database Explorer window.
If the database does not have any favorites defined, AQT will show the Objects display.
For DB2 for iSeries, table names can be referenced using schema/table-name, rather than schema.table_name. Example:
select * from QSYS2/SYSTABLES
This is known as the *SYS Naming Convention. You may wish to adopt this standard if you are running scripts that refer to tables using this convention.
If so, you need to:
This specifies the number of entries in the object-list cache in the Database Explorer. Specify 0 to disable this feature. This value applies to each Database Explorer window, as each Database Explorer window has it's own cache.
The cache is held in memory; the larger this value, the more memory will be used by AQT. You should avoid specifying an unnecessarily high value.
f this value is changed, it won't come into effect until the next time you connect to a database.
History Cache will not be used if Disk Cache is enabled.
When using the Query Builder or the Link to Related Table feature of AQT, AQT needs to find information on table relationships. It get this from two places:
If you do not have any relationships defined to the database, the database query is superfluous and adds unnecessary overhead to AQT. In this case, you may wish to select this option. When this is done, AQT will not query the database for foreign key relationships - it will get related table information from UDRs only.
This option relates to a problem which occurs when you have a large number of objects in the object-list, plus a filter applied so that only a small number of these rows are displayed.
In this circumstances, AQT can be very slow to load the Generate DDL window, the Add Multiple Objects to Favorites window, and (in some cases) the Manage Multiple Objects (such as Drop Table) The slow time is because AQT is loading all the objects into the grid on these windows, then reapplying the filter.
If you are experiencing this problem, you should select this option. In this case, AQT will only load into these windows the objects which are displayed in the object-list. These windows will load much faster. The drawback is that the filter-box on these windows will be disabled; if you wish to have a different filter you will need to return to the Database Explorer window, change the filter, then reinvoke the sub-window.
The displays in the Database Explorer window are obtained by running queries on the system tables. For Oracle, by default, the queries use the ALL system views (such as ALL_OBJECTS). These views only display the objects to which you have access.
When you select this option, AQT will instead use the DBA system views (such as DBA_OBJECTS). These will show you all objects, irrespective of whether or not you have access to them.
The DBA system views are generally not publically available. You should only select this option if you have access to these. If you do not have access to these views, when you use the Database Explorer you will get the message:
ORA-00942: table or view does not exist
This option comes into effect immediately so can be changed during the course of an AQT session, though you may have to Refresh the middle grid and/or the Object Tree if they contain cached information.
When this option is selected, AQT will remember the schema filters between AQT sessions.
When the Disk Cache is enabled, AQT will cache the Database Explorer displays to disk. This is similar to the History Cache, however has a number of advantages:
If your system has a large number of database objects, enabling Disk Cache will result in a faster startup once you connect to a database.
Specify the following options:
The directory cache files are held in is given in Options > File Locations