Use the Database/Schemas tab to define Source Databases and change Result/Metadata Databases. Once changes are made, they are saved for that data source for future connections.
This tab is labeled Databases when connected to Teradata, and Schemas when connected to Aster, based on each system’s nomenclature for data sources. Consequently, references to data sources in this menu refer to Databases when connected to Teradata and Schemas when connected to Aster.
Connection Properties: Databases tab
The Databases/Schemas tab contains the following fields:
- Source Databases/Schemas — By default, the Source Database/Schema is the Default Database/Schema defined in the Teradata ODBC data source. This is the data source where the tables to be analyzed exist. Other data source are added by selecting Add. Similarly, data source are removed by selecting Remove. To sort the data source alphabetically, select Sort; otherwise, both are displayed here and in the pull-down of the database/schema selector on the Analysis Input screen in the order they are added.
- Result Database/Schema — The name of the data source specified as the Result Database/Schema. By default, this is equivalent to the Userid defined in the ODBC data source, but it can be modified. This is the data source where TWM builds result tables/views.
-
Save to Local Files – This feature redefines the way projects are saved from and loaded into the Project Explorer work area. When this option is checked, requests to save or load projects to/from metadata are satisfied by exporting/importing projects into a folder on the client machine. This allows a user with no permanent space allocated in the data source to save and retrieve projects locally (typically at a considerably faster rate). However, there are the following restrictions to this feature:
- This feature is not available in batch processing (that is, a Metadata Database is required).
- The Add Existing Analysis function is not available with this feature.
- Metadata Maintenance is not available with this feature.
- The standard Archive function is not available with this feature (but Auto-Archive is).
See TWM Data Mining Projects for more information.
- Metadata Database/Schema — The name of the data source specified as the Metadata Database/Schema. By default, this is equivalent to the Userid defined in the ODBC data source, but it can be modified. This is the data source where the TWM metadata has been built.
- Statistical Test Database/Schema — The name of the data source specified as the Statistical Test Database/Schema. By default, this is equivalent to the Userid defined in the ODBC data source, but it can be modified. Set this to the data source where the TWM Statistical Test Metadata was built using the Load Statistical Test Metadata program item.
-
Publish Database/Schema — The name of the data source specified as the Publish Database/Schema. By default, this is equivalent to the Userid defined in the ODBC data source, but it can be modified.
This is the data source where the TWM metadata supporting the Publish analysis will be built on request (see the option). For more information on the TWM publish DB, installing the Teradata Model Manager, and creating the metadata database, see Teradata Warehouse Miner Model Manager User Guide (B035-2303). This step grants all privileges on this data source to the Model Manager user.
- Advertise Database/Schema — The name of the data source specified as the Advertise Database/Schema. By default, this is equivalent to the Userid defined in the ODBC data source, but it can be modified. This is the data source where the TWM Advertise Output Metadata tables, views, and macros are created (see the option ).
- Always Advertise — When checked, the Advertise Output option is assumed to be on for all projects and analyses executed. When this is the case, the corresponding check box on individual output panels is disabled and assumed to be checked. For more information, see Advertise Output.
Click OK to save changes and exit, or Cancel to exit without saving any changes.