Database Cache Inheritance
If the Data Source Explorer Load option is set to show databases in hierarchical format, child databases and user objects are nested under the parent database or user object. When you select a database or user object to be cached, all of its child database and user objects are also cached. When you change the Data Source Explorer Load option, the database cache is deleted and then re-cached using the new selections.
Progress Monitor
- Select .
- Click OK.
- Select .
- Select General.
- Clear the Always run in background check box.
- Click Apply and Close.
About Refreshing Cache
After the cache is created, click Refresh to load the cached databases from the database cache file. Cached databases are identified with the cache icon .
If new database objects are modified in the database while they are loaded from the database cache, the modified objects do not appear in the Data Source Explorer until you refresh the database cache. To refresh the database cache for a specific database, right-click the cached database and select . This action deletes the database cache file, launches a new background job to create a new database cache file, and refreshes the list of databases.
You can also refresh the database cache by deleting the database cache files in the Teradata JDBC Connection Properties dialog. The Data Source Explorer shows any changes to the database objects. A subsequent refresh of the Databases folder loads the database from the database cache file.
Termination of Cache Job
Terminating the database cache job deletes the database cache files and databases to be loaded from the database metadata. To restart the database cache job, you must disconnect and reconnect the Connection Profile, then click the Databases folder to open it and create the database cache files.